• 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. Schematic Pcell : internal node probing

Stats

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

Schematic Pcell : internal node probing

mihirDesai
mihirDesai over 7 years ago

Hi,

Is it possible to probe internal nodes for a stacked Schematic pCell.

I have a stack config where multiple transistors are stacked and want to probe internal node.

When I try this through normal method it does not seem to work.

1. in the ADE XL window -> Outputs -> To BE Saved -> select on Design.

2. Then I select the internal node

But this does not add the signal in the Outputs subwindow in the ADE XL Editor.

I tried to check the netlist but it doesnot show there also.

Thanks,

Mihir

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

    Hi Mihir,

    it may be that your schematic pcell doesn’t have the wires associated with thel nets. Strictly speaking for netlisting the connectivity is all that is required, and the physical drawing isn’t needed or if provided by the pcell doesn’t have to be completely defined the way that a hand drawn schematic would. 

    So most likely this is down to a flaw in the schematic pcell code. We could check that via customer support if we can look at the setup. One way to check is to select the wire in the schematic pcell and then in the CIW type:

    geGetSelSet()~>net~>name

    if this returns (nil) then it’s not set up correctly - compare with a normal (check-and-saved) schematic. 

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mihirDesai
    mihirDesai over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the quick reply!

    I did run the command on one net and it does show correct net name there. Also netlisting the schematic shows correct internal nodes so I am thinking that should be fine.

    Essentially in the code I am doing the following the draw wires.

    wire = dbCreateLine(cv list("wire" "drawing")
                                      list(lx:ly ux:uy)
                                    )
    wire~>net = nl1

    Is this correct or something more needs to be done ?

    Thanks,

    Mihir

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mihirDesai
    mihirDesai over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for the quick reply!

    I did run the command on one net and it does show correct net name there. Also netlisting the schematic shows correct internal nodes so I am thinking that should be fine.

    Essentially in the code I am doing the following the draw wires.

    wire = dbCreateLine(cv list("wire" "drawing")
                                      list(lx:ly ux:uy)
                                    )
    wire~>net = nl1

    Is this correct or something more needs to be done ?

    Thanks,

    Mihir

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to mihirDesai

    The fact that it netlists ok doesn’t prove anything since that only looks at the connectivity and not the link between physical objects (the wires) and the connectivity. 

    What you’ve described seems reasonable and should work. Similar constructs work fine for me. Could you contact customer support so that we can take a look (ask them to involve me if the AE can’t resolve it).

    Regards,

    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