• 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. Concept HDL Bus connection

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 164
  • Views 13497
  • 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

Concept HDL Bus connection

archive
archive over 17 years ago

In my design i am having Bus PPC_A.it is splitted as PPC_A to NVRAM and PPC_A to Flash device.From this  memory block i want to take only one signal into top level called PPC_A.So how to combine those signal into PPC_A signal.

Please help me.

Thanks in Advance.


Originally posted in cdnusers.org by lingam
  • Cancel
  • archive
    archive over 17 years ago

    Hello,
    The tool should do this automatically for you. However, to make my schematic easier to read, I always stick to the following conventions:

    When I draw a bus, I always show the entire scope of the bus. So in your case, if the bus is PPC_A<10..31>, and I only need <10..24> then I would always draw <10..31>, and then only create taps for <10>, <11>.... <24>.

    When jumping heirarchy levels, the same rule applies. Show the entire scope. Doens't matter if the upper level onyl requires 1 bit, I still connect them all. The resultant netlist is the same.

    Finally, I never use vectored pins on components. Hierarchical blocks are fine (you can change the number of bits to suit your need). Personally I find that it aids debug to show discrete pins on components. You will also avoid the pain of getting your design back to find that bit 0 is connected to 31, 1 to 30 etc.
    Hope that helped.


    Originally posted in cdnusers.org by vealmic@uk.ibm.com
    • 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