• 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. incomplete nets

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 93
  • Views 15124
  • 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

incomplete nets

crystee
crystee over 13 years ago

Hi all,

i am working with soc -encounter. while routing the design no violations were reported.
but when verified with calibre -lvs its showing 4 incomplete nets. when checked for same nets in soc - E those are no connected/routed as required.
what would be the reason & how to overcome such violations.

should these nets must be routed manually?

Thanks

  • Cancel
  • Anjana
    Anjana over 13 years ago

    Yes , route them manually

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • wally1
    wally1 over 13 years ago

    If you run Verify Connectivity in Encounter do these nets get reported as open? If they do, NanoRoute should route them assuming they are signal nets and they have not been excluded from routing (setAttribute -net netName -skip_routing true). If Verify Connectivity does not report the open then double check that the Verilog netlist defines the connectivity. If these are power/ground nets make sure globalNetConnect was run to define their connectivity and use power planning commands (addRing, addStripe, sroute) to route them.

    Regards,

    Brian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • crystee
    crystee over 13 years ago

    Verify Connectivity does not report any violations. When taken to calibre for LVS, these nets are reported as incomplete.

    When checked back in SoC-E these are not connected as intended.

    These are not power/ground nets.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

    what does one of these nets look like in the verilog or def?

    try running verify connectivity on the specific net name.

    not sure what's going on, just some ideas to try...

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • crystee
    crystee over 13 years ago

    Hi all,

    Thanks for your suggestions, finaly found out the reason behind the problem.

    The netlist provided was not made case-sensitive. In design which were reported as incomplete nets are all case senstive.

    This we can found out by checking in Tools --> schematic viewer of SoC-E.

    When i tried it showed 2 nets of same name with case sensitivity like N97 & n97. By making the netlist case sensitive the problem is solved.

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • nimay
    nimay over 12 years ago

     Hi,

    How did you make your netlist case sensitive?

    Nimay

    • 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