• 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. RF Design
  3. zpm can't be evaluated

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 63
  • Views 5733
  • 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

zpm can't be evaluated

amitG22
amitG22 over 5 years ago

Virtuoso Version -- IC6.1.7-64b.500.23

Cadence Spectre Version -- 17.10.515

I have a very simple circuit. Please find attached. It is basically a resistor across a port. I run a S-param simulation and can plot the S-params, but unfortunately not the Z-param or Y-param. 

/resized-image/__size/320x240/__key/communityserver-discussions-components-files/33/Capture_5F00_Sch.JPG

/resized-image/__size/320x240/__key/communityserver-discussions-components-files/33/Capture_5F00_Error.JPG

Can anyone point me in the correct direction to sort out this problem? The zpm does work in another design environment, but not in the new design environment (a new project). The virtuoso and the cadence-spectre versions match in both the project environments. I am at a loss at what to look for. 

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

    The pictures are rather hard to see, but the problem is that somebody in your environment has done:

    setVarWriteProtect('name)

    and that is killing the code. It appears to me that the problem only occurs if you have zpm('sp 1 1) in the ADE outputs. 

    I suspect you'd also get an error if in the CIW you do:

    foreach(name list(1 2) println(name))

    You need to find wherever this setVarWriteProtect('name) is being performed and remove it. Write protecting a variable with a simple name like this is just asking for trouble.

    Regards,

    Andrew.

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

    The pictures are rather hard to see, but the problem is that somebody in your environment has done:

    setVarWriteProtect('name)

    and that is killing the code. It appears to me that the problem only occurs if you have zpm('sp 1 1) in the ADE outputs. 

    I suspect you'd also get an error if in the CIW you do:

    foreach(name list(1 2) println(name))

    You need to find wherever this setVarWriteProtect('name) is being performed and remove it. Write protecting a variable with a simple name like this is just asking for trouble.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Andrew Beckett

    I should point out that if I enter zpm('sp 1 1) in the calculator and try to plot from there, it worked even with this variable write protected. Also if I used the direct plot form and hit the ZP button.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amitG22
    amitG22 over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for replying back.

    I have tried using zpm in the calculator as well as using it from the "Direct Form" option. It still didnt work.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to amitG22

    It's possible that I got lucky in the version I was using - I was not proposing the calculator or direct plot as a solution, . You need to remove this setVarWriteProtect, as it's likely to break all sorts of things.

    Maybe try running "virtuoso -nocdsinit" and see if that fixes it? It may give you somewhere to start looking if this is something loaded from a .cdsinit somewhere. There should not be an error about "name" being write protected unless somebody has explicitly done this somewhere.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amitG22
    amitG22 over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks. I will get in touch with the responsible person on Monday and try the "nocdsinit" solution too. I will provide an update afterwards.

    Thanks a lot.

    Regards,

    Amit

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amitG22
    amitG22 over 5 years ago in reply to Andrew Beckett

    #### UPDATE ####

    Hi Andrew,

    Just updating this thread with the current status. 

    You were right about the solution. Our CAD team was able to find the root cause to an internal tool loaded in the cdsinit file. Removing that tool, solves our issue with the Z/Y parameters. 

    Thanks a lot for your help.

    Regards,

    Amit

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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