• 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 short circuit in layout for analogLib\iPRB kind behavioural...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 2603
  • 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 short circuit in layout for analogLib\iPRB kind behavioural cell

DavidLou
DavidLou over 6 years ago

hello experts,

I noticed from other post that lxRemoveDevice  which can remove devices and short in the process. but that's some script to process while netlisting. can we set some property in the symbol like "nlAction" = ignore as basic/noConn. is there similar user property we can set to get remove the current cell and short the terminals when layout/lvs/drc, etc?

thanks,

David

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

    Hi David,

    It's not a "script to process while netlisting". It's the property you use to tell either VLS XL or the netlisters (if you've enabled it). The documentation explains how to use them - search for lxRemoveDevice.

    nlAction=ignore won't work because that just tells the netlist to omit the device, and gives no information about how to short the terminals.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    yup, putting lxRemoveDevice as User Property works.

    thanks Andrew,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    yup, putting lxRemoveDevice as User Property works.

    thanks Andrew,

    David

    • 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