• 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. Bottom-Top design using Concept HDL..

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 166
  • Views 17589
  • 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

Bottom-Top design using Concept HDL..

MAAC
MAAC over 16 years ago

Hi,

I would like to know the Bottom-Top design approach in HLD...or hierarchical design from Bottom to top..???

Which is prefered one Top-Bottom or Bottom-Top??...I could able to do the Top-Bottom design using Concepthdl_tut.pdf from Doc....

How can we do the Bottom-Top design r is there any user guide for the same.(not the Tools-Genview)

 

Thnx

  • Cancel
  • EvanShultz
    EvanShultz over 16 years ago

     Hi MAAC,

    I typically do bottom>top work. Here is the procedure that I use:

     1. Create a new project. Open the schematic (you'll be at the 'root' page) and go to File > New. This will be your hierarchical block schematic.

    2. Once you're composed the circuitry for the block, leave the nets that go to the ports (pins of the block) dangling.

     3. Go to File Save As to save this schematic page as a Cell. In addition to naming the cell, make sure the View is Schematic. Accept the errors/warnings when saving.

    4.  Add ports to the design and name those nets that leave and hierarchical block. Save again.

    5.  Go to Tools > Generate View. I accept the default settings, click Generate then Done, and close the schematic page. You're now back at the 'root' schematic page.

    6. Using the Component Browser, you can add the hierarchical block from the project's root library like any other component.

    7. Once placed, you can manipulate the block by pulling it up with File > Open. The changes will automatically propogate to the 'root' level.

     

    Is that what you're looking for?

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

    Thnx Evan,

    ....:):)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Samuel Zhang
    Samuel Zhang over 14 years ago

    How to deal with power pins for the reuse blocks? When I add an outport with the signal name "+5V_USB" to the block, an error appears: Schematic has port but port does not exist in the symbol. Either delete this port from the schematic or add this port in the symbol.

    Does it mean I can't add power port to reuse blocks?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Jerry GenPart
    Jerry GenPart over 14 years ago
    This error usually means that since you added an OUTPUT symbol with the signal name "+5V_USB", it needs to see this same logical pin name on the hierarchical block that represents this logical schematic. If you don’t need to bring the "+5V_USB" signal to the hierarchical block symbol, then just remove the OUTPUT symbol attached to the "+5V_USB" signal/wire.

    Jerry
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Samuel Zhang
    Samuel Zhang over 14 years ago
    Hi Jerry, Thank you so much for your response.

    This error also appears when I modify a reuse module. I want to modify a reuse module that has already been placed into a board layout. When I modify the subdesign schematic and save it, errors appear: ERROR(SPCOHD-168):Schematic has port but port does not exist in the symbol. Either delete this port from the schematic or add this port in the symbol.Then I cannot package the subdesign schematic. I just changed some signal names of the subdesigns. I don't know why these errors exsit even I delete all the modules in the top-level schematic.
    Could you please help me to solve it?

    Thanks.
    Best Regards,
    Samuel

     

    • 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