Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 1543
  • 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

output pin connected to power/ground net

archive

Hello,
I was trying to place and route a design with SOC Encounter after power planning and synthesis.

My earlier trials of place and route without power nets were going relatively smoothly. After synthesizing power plan, I started to get many (~40) messages like

**WARN: (SOCDB-2078):   Output pin Y of instance x0 is connected to ground net n_2.
**WARN: (SOCDB-2078):   Output pin Y of instance x1 is connected to ground net n_1.
**WARN: (SOCDB-2078):   Output pin Y of instance x2 is connected to power net n_15.
**WARN: (SOCDB-2078):   Output pin Y of instance x3 is connected to power net n_14.
**WARN: (SOCDB-2078):   Output pin Y of instance x4 is connected to power net n_13.
...
...

I was wondering if anyone has dealt with this warning? I cannot make any sense of it. Many thanks in advance.

-aydin


Originally posted in cdnusers.org by balkanay

  • Update:
    In case anybody faces this problem, I was able to eliminate warnings by giving unique names to all power/gnd nets, such as n_pwr_1, n_gnd_2, instead of using the synthesizer-generated generic net names such as n_1, n_2.


    Originally posted in cdnusers.org by balkanay

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.