• 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. check instance binding layout Vs Schematic

Stats

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

check instance binding layout Vs Schematic

jaapvds
jaapvds over 2 years ago

I would like to check per instance the binding (XL compliancy) between Layout and Schematic.

Function bndGetBoundObjects can be used for this purpose, like:

foreach(insts cvId~>instaces

   bndGetBoundObjects(insts)

....

However this must be ran in XL mode

To overcome this, function lxRunCmdInXL should be used, however when using:

foreach(insts cvId~>instaces

  lxRunCmdInXL(cvId  'bndGetBoundObjects insts) 

....

I get the error: *Error* lxRunCmdInXL: extra arguments or keyword missing - ((db:0x5d0ef89a db:0x5d0ef89b))

What extra argument must be added?

Thanks!

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

    Two issues:

    1. You need to pass the argument list to lxRunCmdInXL with ?cmdArgs (which needs to be a list)
    2. The function always gets passed the layout and schematic cellView ids. 

    You could do:

    procedure(MyWrapBndGetBoundObjects(_d1 d2 instId)
      bndGetBoundObjects(instId)
    )
    bindings=foreach(mapcar inst cv~>instances lxRunCmdInXL(cv  'MyWrapBndGetBoundObjects ?cmdArgs list(inst)))

    However, it is probably best to just to "run in XL" once (this will be much quicker, as XL only gets initialised a single time):

    procedure(MyGetAllBindings(lcv _scv)
      foreach(mapcar inst lcv~>instances bndGetBoundObjects(inst))
    )
    bindings=lxRunCmdInXL(cv 'MyGetAllBindings)

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jaapvds
    jaapvds over 2 years ago in reply to Andrew Beckett

    I have following instances in my design:

    Bound M0 - MOS transistor from Foundry lib
    Bound M1 - MOS transistor from Foundry lib
    UnBound I0 
    UnBound I1
    Bound PIN0 - VDD pin from analog lib
    Bound PIN1 - gnd pin from analog lib

    output from bindings=lxRunCmdInXL(cv 'MyGetAllBindings):

    ((((db:0x5f13c59a 0 0 0)))
    (((db:0x5f13c59b 0 0 0))) nil nil
    ((db:0x5f13129a))
    ((db:0x5f13129b))
    )

    I suppose the two 'nil' in the output indicate the unbound instances I0/I1?

    (db:0x5f13c59a 0 0 0)  and (db:0x5f13c59b 0 0 0)) - indicates M0/M1

    and

    (db:0x5f13129a) and db:(0x5f13129b) - indicates PIN1/PIN0

    So why are differences between MOS (db object and 2 '0') and PIN with only db objects?

    Because if I extend your procedure with:

    foreach(mapcar insts lcv~>instances
    totalInsts = totalInsts+1
    boundUnbound = 0
    if(bndGetBoundObjects(insts) then
    listGbound = cons(insts listGbound)
    printf("Bound Inst %s \n" insts~>name)
    printf("Bound Schem Inst %s \n" caaar(bndGetBoundObjects(insts))~>name)
    else
    listUbound = cons(insts listUbound)
    printf("Unbound Inst %s \n" insts~>name)
    ); if
    ) ;foreach

    I get the following error message:

    Bound M0
    Bound M1
    UnBound I0
    UnBound I1
    *Error* car: Can't take car of atom - db:0x5f13129a

    Any idea how to solve this?

    thanks!

    Jaap

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jaapvds
    jaapvds over 2 years ago in reply to Andrew Beckett

    I have following instances in my design:

    Bound M0 - MOS transistor from Foundry lib
    Bound M1 - MOS transistor from Foundry lib
    UnBound I0 
    UnBound I1
    Bound PIN0 - VDD pin from analog lib
    Bound PIN1 - gnd pin from analog lib

    output from bindings=lxRunCmdInXL(cv 'MyGetAllBindings):

    ((((db:0x5f13c59a 0 0 0)))
    (((db:0x5f13c59b 0 0 0))) nil nil
    ((db:0x5f13129a))
    ((db:0x5f13129b))
    )

    I suppose the two 'nil' in the output indicate the unbound instances I0/I1?

    (db:0x5f13c59a 0 0 0)  and (db:0x5f13c59b 0 0 0)) - indicates M0/M1

    and

    (db:0x5f13129a) and db:(0x5f13129b) - indicates PIN1/PIN0

    So why are differences between MOS (db object and 2 '0') and PIN with only db objects?

    Because if I extend your procedure with:

    foreach(mapcar insts lcv~>instances
    totalInsts = totalInsts+1
    boundUnbound = 0
    if(bndGetBoundObjects(insts) then
    listGbound = cons(insts listGbound)
    printf("Bound Inst %s \n" insts~>name)
    printf("Bound Schem Inst %s \n" caaar(bndGetBoundObjects(insts))~>name)
    else
    listUbound = cons(insts listUbound)
    printf("Unbound Inst %s \n" insts~>name)
    ); if
    ) ;foreach

    I get the following error message:

    Bound M0
    Bound M1
    UnBound I0
    UnBound I1
    *Error* car: Can't take car of atom - db:0x5f13129a

    Any idea how to solve this?

    thanks!

    Jaap

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

    Not sure which direction you're going in, but using bndGetBoundObjects on a schematic pin will give the corresponding layout terminal and vice versa. These are not returned as a list in the same way because they don't need to have either a hierarchical path nor would they need the array indices that you get with instances. Your code has caaar(bndGetBoundObjects(insts))~>name) which assumes that has the list structure for an instance.

    The documentation seems to not mention this - it probably should... (I've fed that back to tech pubs).

    Andrew

    • 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