Stats

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

Cadence Schematic - customizing DC Operating Points annotation permanently

firebolt

I can customize operating points displayed on schematic temporarily using Annotation Setup. There is a option to save the setup. On relaunching Cadence or for different schematic, I have to setup again. Is there a way to modify the list permanenlty using cdsinit or any other method?

  • firebolt
    in reply to Andrew Beckett

    Thanks Andrew. How to remove this yellow text definition? It's not in annotation setup.

  • Andrew Beckett
    in reply to firebolt

    Assuming that this label on the symbol is on the device/annotate layer purpose pair (which is the usual convention for a [@cellName] NLP label), you can turn them off using:

    techGetLP(techGetTechFile(geGetEditCellView()) '("device" "annotate"))~>visible=nil hiRedraw()

    Other than changing the technology file to turn off visibility of device/annotate by default, there's not really a way of doing it by default. I guess you could put:

    techGetLP(techGetTechFile(ddGetObj("gpdk045")) '("device" "annotate"))~>visible=nil

    or similar in your .cdsinit - replacing gpdk045 with your technology library name. You can then get them back by using View->Show Instance Labels in the schematic editor.

    Andrew

  • firebolt
    in reply to Andrew Beckett

    Thanks Andrew. These cdsinit definitions are working.

    To set default annotation -> envSetVal("auCore.misc" "annotationSetupFileList" 'string “<pathToMyAnnotationSetup>.as")

    To set bindkey for DC op annotaion -> hiSetBindKey("Schematics" "2" "annLoadAnnotationData(hiGetCurrentWindow() \"<pathTo/.cadence/DCannotationSetup.as>\")")

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.