• 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. Connect two nodes with different names

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 124
  • Views 21585
  • 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

Connect two nodes with different names

archive
archive over 18 years ago

Hi All,

I would like to short-circuit two nodes with different names.
I have a 24 bits vector (let's say vect) and would like to connect each of that node to either V3V or GND. I've used patch (from basic library) but it gives a warning (V3V collides with signal name vect for instance). However it gives no fault during simulation.
Is that good anyway and does it exist other connector? It should be LVS transparent in order to be used for tapeout.

Thks in advance,
Regards,

Axel


Originally posted in cdnusers.org by axp
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Axel,

    You should be able to use patch from basic (or Add->Patchcord in the schematic editor) to alias nets. The patch component can alias both single (scalar) nets and bus/bundle (vector) nets. The one thing you can't do is to alias two different terminals, two different global nets, or a terminal to a global net. For that, you can use the "cds_thru" component in basic. cds_thru ends up as something equivalent to a short in all the things it gets netlisted to - so for Verilog, it's a true through connection (because you can do that in Verilog); for spectre it's an "iprobe" (effectively a zero-volt source); for hspice it's a zero-volt source; for VirtuosoXL it will get shorted by VXL because it has lxRemoveDevice on it; for CDL it ends up as a small resistor (which generally can be shorted by the physical verification tool); and for Diva it ends up as a component that can be removed using removeDevice() in your LVS rules.

    That said, you should only use cds_thru for cases where patch can't be used. patch is a direct alias in the database, so that's better than introducing a real component in circuit simulators, say.

    Best Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Axel,

    You should be able to use patch from basic (or Add->Patchcord in the schematic editor) to alias nets. The patch component can alias both single (scalar) nets and bus/bundle (vector) nets. The one thing you can't do is to alias two different terminals, two different global nets, or a terminal to a global net. For that, you can use the "cds_thru" component in basic. cds_thru ends up as something equivalent to a short in all the things it gets netlisted to - so for Verilog, it's a true through connection (because you can do that in Verilog); for spectre it's an "iprobe" (effectively a zero-volt source); for hspice it's a zero-volt source; for VirtuosoXL it will get shorted by VXL because it has lxRemoveDevice on it; for CDL it ends up as a small resistor (which generally can be shorted by the physical verification tool); and for Diva it ends up as a component that can be removed using removeDevice() in your LVS rules.

    That said, you should only use cds_thru for cases where patch can't be used. patch is a direct alias in the database, so that's better than introducing a real component in circuit simulators, say.

    Best Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • 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