Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14945
  • 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

Analog stimuli in ADEXL error

rkic

I have created a pwl source using the analog stimuli option for a particular pin.

The pwl source has many variables (like slew rate, amplitude etc) which is defined in my design variable section of the test.

When i netlist the test, it netlists fine, there are no errors.

But when i try to run a simulation, i get the error " *WARNING* asiiEvalDesignValList: problem with variable slew

*Error*   in the Design Variables.  AEL's message:  data type error:
          cannot undefer "slew"

It feels like the analog stimuli are being read in before the design variables in some way, since in the design variables section i have the variable "slew" defined.

How should i overcome this error?

  • I forgot to add that all the variables in my pwl have the same error not just the slew.

  • In the netlist, i do see all the parameters defined and the stimuli file being read at the very end, so my guess is that the parameters have been read in. So any ideas on what the source of the error could be? Do the order of the parameters matter? Should i first have the independent paraneters defined and then the dependant parameters?

     

  • I think I've only seen this being an issue when you have dependent expressions in rare cases. Anyway, there's a CCR, 715614, which talks about this - and it is planned (it says for an IC615 hotfix) - but I've not seen it actually be integrated.

    I would suggest that you file a service request and reference this CCR number and ask for a duplicate to be created - ideally with a simple example which shows the problem. That will increase the likelihood of it being fixed sooner rather than later, and the AE can then see if there's a workaround in the meantime.

    Andrew.

  • Thanks for your prompt reply Andrew. I will follow up.

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.