• 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. PCB Design
  3. Hierarchical Net Naming

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 165
  • Views 10857
  • Members are here 0
More Content
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

Hierarchical Net Naming

qa3416
qa3416 over 4 years ago

Hello,

I was wondering if someone could give me some advice on how to set up my Cadence DE HDL (17.2) hierarchical design. To start with a test schematic, I set up the following:

1. top level design is called "Top"

2. Created a sub-block called "PIN_CNTL". The block consists of a resistor with an input IN1 and an output OUT2 and another resistor with IN2 and OUT2.

3. Copied PIN_CNTL three additional times, so now I have a total of four instantiations.

4. Did a "Save Hierarchy" and "Export Physical" -- no errors

When I "descend" into each block, the net naming isn't what I'd expect. In the first block, it appends nothing to the net -- the nets are IN1, IN2, OUT1, OUT2. But when I descend into the 2nd block, the nets are "IN1_1", "IN2_1", "OUT1_1", and "OUT2_1". To me, this is confusing. Since this is the 2nd block, I'd like the appendices to be "_2". In summary --

What Cadence DE HDL named for nets:

1. Block 1: IN1, IN2, OUT1, OUT2

2. Block 2: IN1_1, IN2_1, OUT1_1, OUT2_1

3. Etc for Blocks 3 and 4.

What I _WANT_ (and is less confusing) -

1. Block 1: IN1_1, IN2_1, OUT1_1, OUT2_1

2. Block 2: IN1_2, IN2_2, OUT1_2, OUT2_2

3. Etc for blocks 3 and 4

Any idea how to force DE HDL to do this? Thank you!

  • Cancel
  • qa3416
    qa3416 over 4 years ago

    Here is a pic of what I have, and notes on what I want it to be.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

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