Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 6717
  • 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

Defining Specifications for an Output

Shimon4773

Hi all, I have a question about "Defining Specifications for an Output"

If in the spec column I write VTEST which is bound to an ocean expression the evaluation is not working and give the following error

"*Error eval unbounded variable"

If I write the ocean expression it self it works.
How can I fix this?

I can not put constant in the spec column because in the real circuit the spec is changing and need to be taken from another output expression. 

Parents
  • Andrew Beckett

    As far as I know (and I've not checked this recently), this should work if you use calcVal("VTEST") in the spec. The documentation still only talks about using variables in the specs (which means VAR()), but doesn't really give much detail and it was supposed to have been updated to also show that calcVal (at least the single-argument version of calcVal to get an output from the same test) should work. There were some limitations (CCR 1442710) but I've not checked recently to see whether they are still there or not.

    Andrew

Reply
  • Andrew Beckett

    As far as I know (and I've not checked this recently), this should work if you use calcVal("VTEST") in the spec. The documentation still only talks about using variables in the specs (which means VAR()), but doesn't really give much detail and it was supposed to have been updated to also show that calcVal (at least the single-argument version of calcVal to get an output from the same test) should work. There were some limitations (CCR 1442710) but I've not checked recently to see whether they are still there or not.

    Andrew

Children
  • Shimon4773
    in reply to Andrew Beckett

    It works, thank you very much it is a real saver.

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.