Stats

  • Locked Locked
  • Replies 3
  • Subscribers 124
  • Views 4732
  • 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

Prevent Maestro from reporting undefined design variables

FormerMember
FormerMember

Hello,

I have a cell view which contains standard elements (resistor, capacitor,...) with variables. I want to set these variables with a model file. However, everytime when I start the simulation, Maestro reports these variables as undefined. If I continue, the simulation fails, because the empty variables are added to the 'parameters' statement, which comes after my model file. 

Is there a way to prevent Maestro from automatically adding undefined variables? I found the 'findVariablesSkip' global variable in the documentation, which seems to do exactly what I want (ignore variables in extracted cell views, if the cell view contains the 'extractionCreatedBy' property). However, even if I set it to 'extracted' or 'parasitic' and add the 'extractionCreatedBy' property to my cell view, Maestro still complains about the variables.

Best regards

Paul

  • FormerMember
    FormerMember

    For now I found a workaround by defining the variables under a different name in the model file and set the automatically added variables in Maestro to these. In this case no empty variables are generated, but this is not really a good solution, because one has to always do this for each testbench and test. Does anyone have another idea to solve this?

  • FormerMember
    FormerMember

    I found a workaround which seems to solve my problem. Instead using a variable, I use a constant function in the expressions. I then define the functions in a model file. However, I will also file a support request, asking if it is also possible to do this with variables.

    I investigated a little bit further and it seems the issue is not caused by Maestro, but during the netlisting process. Even if I netlist the cell view directly, the empty variables are always added.

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.