Stats

  • Locked Locked
  • Replies 3
  • Subscribers 165
  • Views 13048
  • 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

Block Designing

TIDVEng

My goal for my current project is to create a Hierarchical Block Library in Cadence for my team and I to use in the future. With that said, here are my questions:

 

 

1) After I have created my hierarchical blocks, how can I export them as a library for my coworkers to import and use in the easiest way possible?

 

2) I would like to use hierarchical blocks inside of hierarchical blocks, is it possible? How does the naming of the larger block propagate to that of the block inside of it? Could you provide instructions on how to use the blocks inside of a block?

 

3) Can we have different versions of a block? My goal is to have a single block with multiple versions of the same said component that would have different configurations.

4) In the component library that I have created, I have extra components in the Component View that I do not want. How can I delete them? (control + delete does not work)

 

 

Thank you for the help, it is very much appreciated.

Parents
  • Wild

    1. I have created HhBlocks as a library item many years ago, it can be done, including the MDD file.

    2. Not sure about the naming, I believe there is a way with atcl tool, but it can be done manually very easy.

    3. A block as a variant is what i believe you are asking, - outside of my experience sorry.

    4. Not sure maybe a refesh cache?

    Wild

Reply
  • Wild

    1. I have created HhBlocks as a library item many years ago, it can be done, including the MDD file.

    2. Not sure about the naming, I believe there is a way with atcl tool, but it can be done manually very easy.

    3. A block as a variant is what i believe you are asking, - outside of my experience sorry.

    4. Not sure maybe a refesh cache?

    Wild

Children
No Data
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.