• 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. reportDanglingPort command problem

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 12972
  • 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

reportDanglingPort command problem

dota
dota over 16 years ago

    I found reportDanglingPort command in encounter Can't report top-level module dangling port, So deleteDanglingPort can't clean these ports. any way to fix it?

  • Cancel
  • BobD
    BobD over 16 years ago

    Hi Dota,

    It sounds like you're working on a block-level design and want to delete top level module port that isn't connected to anything.  reportDanglingPort and deleteDanglingPort both work on hierarhical instances in the design (not on top level module ports).  I wouldn't be surprised if the tool doesn't provide this capability for fear of changing the top level port list and causing downstream formal verification failures.

    There may be a native way to achieve what you're looking for, but if there is I'm not aware of it.  Maybe you could try a scripted approach that identifies the top level module ports that have only 1 term (ie, itself) and then you can call deleteModulePort with the "-" option (which is a special operator for the top level module) to delete the top level module port?

    foreach term [dbGet top.terms] {
      if {[dbGet $term.net.numTerms] == 1} {
        deleteModulePort - [dbGet $term.name]
      }
    }

    Hope this helps,
    Bob

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BobD
    BobD over 16 years ago

    Hi Dota,

    It sounds like you're working on a block-level design and want to delete top level module port that isn't connected to anything.  reportDanglingPort and deleteDanglingPort both work on hierarhical instances in the design (not on top level module ports).  I wouldn't be surprised if the tool doesn't provide this capability for fear of changing the top level port list and causing downstream formal verification failures.

    There may be a native way to achieve what you're looking for, but if there is I'm not aware of it.  Maybe you could try a scripted approach that identifies the top level module ports that have only 1 term (ie, itself) and then you can call deleteModulePort with the "-" option (which is a special operator for the top level module) to delete the top level module port?

    foreach term [dbGet top.terms] {
      if {[dbGet $term.net.numTerms] == 1} {
        deleteModulePort - [dbGet $term.name]
      }
    }

    Hope this helps,
    Bob

     

    • 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