• 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. Custom IC Design
  3. Two Environment Setup Issues

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 12801
  • 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

Two Environment Setup Issues

Kevin Buck
Kevin Buck over 3 years ago

I'm trying to figure out two Cadence environment issues. I have found what I believe are the correct environment variables but the tool doesn't seem to be responding to them.

First issue: scalar expressions are being plotted in Maestro instead of evaluating a number. I've chosen the stability summary 'Add to Outputs' option and I'm used to this just evaluating a number for phase margin and unity gain frequency but for some reason in the environment I'm working in this data evaluates to a wave. I have opened the 'Plot Options' window and unchecked the 'Plot Scalar Expressions' option but it still evaluates as a wave and gets plotted as a figure instead of a number. I've also tried adding the following expressions to my .cdsinit and .cdsenv files but neither works:

envSetVal( "adexl.plotting" "plotScalarExpressions" 'boolean nil )

adexl.plotting plotScalarExpressions boolean nil

Additionally, I also tried setting the plotScalarsAsLine variable to nil although it does not look like this is the variable I'm interested in from the support manual description.

Second issue: schematic view is not the default value populated in the descend window when browsing hierarchies. I'm not using a Maestro view I'm just browsing schematics and when I descend into a block that contains a verilog view it automatically prompts for verilog which is VERY annoying since my muscle memory just strikes the enter key immediately (but I do also like to retain the option of changing the view when I want to). I went to the Options -> Editor window under the Commands tab and changed the 'View Name List' to begin with schematic symbol and so on. When I make this selection I get the desired behavior, namely that the schematic view is selected by default when the descend window opens. I used this to find the altered command in the Cds environment editor and added the following to the .cdsenv file:

schematic viewNameList string "schematic symbol behavioral functional system verilog pld_verilog lai_verilog lmsi_verilog"

This does not change the behavior of the tool, I have to manually change the 'View Name List' option every time I open the tool to get the desired behavior.

I'm using Cadence version 6.1.8-64b.500.9

  • Cancel
Parents
  • Kevin Buck
    Kevin Buck over 3 years ago

    An update for the second problem as I had time to circle back and look at it again.

    It seems that I am editing the correct environment variable (viewNameList) and that it is set correctly by the .cdsinit file. When I open the Cdsenv Editor from a fresh Cadence session I see the expected modification, but when I descend into a cell that contains a verilog view I'm still by default prompted to open the verilog view even though schematic is the first view listed on the viewNameList environment variable. If I open the 'Options->Editor' menu in the schematic the 'View Name List' option still does not reflect what is found in the Cdsenv Editor window and in the .cdsinit file. If I then modify the 'View Name List' menu to something else the Cdsenv Editor menu viewNameList is updated. For example if I place the symbol as the first instance on the list and press apply the viewNameList parameter in the Cdsenv Editor menu looks like this:

    If I place schematic as the first name in the list and press apply the Cdsenv editor places schematic at the beginning of the list just like when the tool is started but now I get the expected behavior when I descend into a cell with schematic as the default view so I can use my hotkey (the default E) and then press enter and descend into the schematic. I'm not sure if this is a bug or if there is some obscure reason that the GUI window isn't loaded with the value in the .cdsinit file.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kevin Buck
    Kevin Buck over 3 years ago

    An update for the second problem as I had time to circle back and look at it again.

    It seems that I am editing the correct environment variable (viewNameList) and that it is set correctly by the .cdsinit file. When I open the Cdsenv Editor from a fresh Cadence session I see the expected modification, but when I descend into a cell that contains a verilog view I'm still by default prompted to open the verilog view even though schematic is the first view listed on the viewNameList environment variable. If I open the 'Options->Editor' menu in the schematic the 'View Name List' option still does not reflect what is found in the Cdsenv Editor window and in the .cdsinit file. If I then modify the 'View Name List' menu to something else the Cdsenv Editor menu viewNameList is updated. For example if I place the symbol as the first instance on the list and press apply the viewNameList parameter in the Cdsenv Editor menu looks like this:

    If I place schematic as the first name in the list and press apply the Cdsenv editor places schematic at the beginning of the list just like when the tool is started but now I get the expected behavior when I descend into a cell with schematic as the default view so I can use my hotkey (the default E) and then press enter and descend into the schematic. I'm not sure if this is a bug or if there is some obscure reason that the GUI window isn't loaded with the value in the .cdsinit file.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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