• 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. How to set / overwrite instance inherited netset property...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14717
  • 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

How to set / overwrite instance inherited netset property in layout view?

sl3j
sl3j over 11 years ago

 How to set / overwrite instance inherited netset property in layout view?

I am trying something like this

dbCreateProp(myInst "vdd"  "netSet"    vdd1)

It does not seem to work, the connectivity in Layout XL does not show any change!

The signal vdd1 already alread exists in the layout.

 Any way to change signal mapping of instance terminals?

 

  • Cancel
Parents
  • sl3j
    sl3j over 11 years ago

     As promessed for sharing the findings,

    here is the solution I propose based on your hints.  It works at the cellview level.

    I have not yet tried if we should map both "gnd" and "gnd!" terminals to enable inherited connection propagation down into the hierarchy,

    thanks

     

    -Sami

     

     

    procedure(SLMapInstTerm(cv InstName TermName NetName)
    let( (myInst myInstTerm myNet )

    if( myInst=dbGetInstanceByName(cv InstName) then

    ; creating new net or getting it if existing
    if( (myNet = dbFindNetByName(mycv NetName))  then
         else  
        myNet = dbCreateNet(mycv NetName)
        printf(" --I-- New Net %s created \n" myNet~>name)
    )
    ; Mapping the terminal by name to the new net
    foreach(myInstTerm myInst~>instTerms
            if(myInstTerm~>name == TermName then
                myInstTerm~>net = myNet    
                printf(" --I-- Connection remapped   %s :  term %s   -> %s\n" myInst~>name TermName  myNet~>name))
            )
    else
        printf(" --W-- Instance Not found : %s \n" myInstName)
    )
    ))
    ;===================


    ; quick test

    mydb=hiGetCurrentWindow()
    mycv=mydb~>cellView

    SLMapInstTerm(mycv "I1" "gnd!" "GND1")
    SLMapInstTerm(mycv "I2" "gnd!" "GND1")

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • sl3j
    sl3j over 11 years ago

     As promessed for sharing the findings,

    here is the solution I propose based on your hints.  It works at the cellview level.

    I have not yet tried if we should map both "gnd" and "gnd!" terminals to enable inherited connection propagation down into the hierarchy,

    thanks

     

    -Sami

     

     

    procedure(SLMapInstTerm(cv InstName TermName NetName)
    let( (myInst myInstTerm myNet )

    if( myInst=dbGetInstanceByName(cv InstName) then

    ; creating new net or getting it if existing
    if( (myNet = dbFindNetByName(mycv NetName))  then
         else  
        myNet = dbCreateNet(mycv NetName)
        printf(" --I-- New Net %s created \n" myNet~>name)
    )
    ; Mapping the terminal by name to the new net
    foreach(myInstTerm myInst~>instTerms
            if(myInstTerm~>name == TermName then
                myInstTerm~>net = myNet    
                printf(" --I-- Connection remapped   %s :  term %s   -> %s\n" myInst~>name TermName  myNet~>name))
            )
    else
        printf(" --W-- Instance Not found : %s \n" myInstName)
    )
    ))
    ;===================


    ; quick test

    mydb=hiGetCurrentWindow()
    mycv=mydb~>cellView

    SLMapInstTerm(mycv "I1" "gnd!" "GND1")
    SLMapInstTerm(mycv "I2" "gnd!" "GND1")

    • 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