• 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 SKILL
  3. Replacing ADE-L variables

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13084
  • 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

Replacing ADE-L variables

ASICnm
ASICnm over 11 years ago

Hello all,

I have several variables from transistor parameters in my design, and I want to hardcode them, before I start doing the layout. My script makes a copy of original schematics first, and then needs to replace the values assigned to variables in ADE-L window, to all those parameters.

Could someone hint how to read the ADE variables and replace the transistor parameter with their value. I start the script like this:

---------------------------------------

;; open original schematic

cvId = dbOpenCellViewByType(myLibName myCvName myViewName)

dbCopyCellView(cvId myLibName myCvName newViewName nil nil t)

;; create a new schematic copy

cvId2 = dbOpenCellViewByType(myLibName myCvName newViewName)

 instId=cvId->instances

;; the following might give me length in my PDK:

car(car(instId~>prop~>value))  ;; e.g. get length

;; now pick up ADE variables 

 

--------------------------------------------

Thanks in advance,

 

 

  • Cancel
  • ASICnm
    ASICnm over 11 years ago

    Ok, that got solved, just needed to find this function to proceed with the rest.

    (asiGetDesignVarList (asiGetCurrentSession))

    Ofcourse further processing is required.

    As a beginner it is often hard to locate the functions..

     

    • 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