• 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. Digital Implementation
  3. Direction of VDD/VSS (inout vs input)

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 5513
  • 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

Direction of VDD/VSS (inout vs input)

drdanmc
drdanmc over 5 years ago

What is the reason that power/ground ports that are added in the physical implementation flow have direction "inout" instead of "input"?  Is there a way to force them to be "input" instead without running some post-processing code?

a simple example is starting with something like this out of synthesis:

module mycell(A, Y);

    input A;

    output Y;

    INVX1 myinst(.A (A), .Y (Y));

endmodule

Then using things like this in the physical place/route:

set init_pwr_net "VDD"
set init_gnd_net "VSS"

globalNetConnect VSS -type pgpin -pin VSS -all
globalNetConnect VDD -type pgpin -pin VDD -all

and ending up with

module mycell(A, Y, VDD, VSS);

    input A;

    output Y;

    inout VDD;  // WHY INOUT

    inout VSS;  // WHY INOUT

    INVX1 myinst(.A (A), .Y (Y), .VDD(VDD), .VSS(VSS));

endmodule

The reason I care is in mixed signal sims (AMS) or even DMS sims, I want to avoid any possibility of bi-directional connect modules whenever possible.  To that end, I'd like to be able to simulate the post-physical design (that includes power/ground) but with those defined as "input" instead of "inout". 

  • Cancel
Parents
  • Dimo M
    Dimo M over 4 years ago

    Hi,
    you can use the switch saveNetlist -derivePGPortDir (CUI: write_netlist -derive_pg_port_dir) to enable Innovus to derive the direction of implicitly created power ports.
    Innovus will trace the connectivity and decide the direction of these ports.
    The port direction will be input if the module contains only sinks (loads).
    What constitutes a source and sink is decided based on UPF (if present) and liberty files.

    Dimo

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Dimo M
    Dimo M over 4 years ago

    Hi,
    you can use the switch saveNetlist -derivePGPortDir (CUI: write_netlist -derive_pg_port_dir) to enable Innovus to derive the direction of implicitly created power ports.
    Innovus will trace the connectivity and decide the direction of these ports.
    The port direction will be input if the module contains only sinks (loads).
    What constitutes a source and sink is decided based on UPF (if present) and liberty files.

    Dimo

    • 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