Stats

  • Locked Locked
  • Replies 9
  • Subscribers 166
  • Views 6232
  • 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

How to place heterogeneous parts in two same hierarchy bolcks(occurrence)?

xiaoyi594

Hi there!

We met a problem in place and annotate heterogeneous parts in hierarchy blocks.

An IC contains dual amplifiers, and it's  schematic symbol consists of two heterogeneous parts(A and B).We use ONE amplifier in a specific hierarchy Block (name is BLOCK_TEST)

There are two Occurrences of BLOCK_TESTs in our project, so one IC is just enough. We attempted to place part A in BLOCK_TEST0 and place part B in BLOCK_TEST1. 

There seems to be paradox: two BLOCK_TESTs is exactly the same occurrences, while the part A and part B is heterogeneous symbol.

How to solve this confilct? 

The example dsn and olb file is attached.

Thanks very much!

cadence_example.zip

  • oldmouldy
    You do need to specify which section(s) of a Heterogeneous part you want to use. Since it would be perfectly acceptable to "only" use the "A" (first) section, or indeed only any one of the sections, of the package in all the blocks, and not use any of the other sections "anywhere" in the design, Capture cannot determine which section(s) to use, regardless. This is not true of Homogeneous parts since all of the sections are identical.
  • Honortronics

    Hi Vid (...and anyone else that can benefit from this),

    I had the same issue and fought it for hours before finding a resolution.  Since there really isn't that much information on the net about this (at least in English), I thought that I would post my findings in hopes that it helps you or someone else.

    I have an extremely complex Hierarchical design that would be far too laborious to rename everything manually so I had to resolve this issue.

    The secret is in the "Physical Packaging - Combined Property String" section of the Annotate box.  Within Property Editor for your design, you create a new User Property, so I just created a new column with the name "Circuit Description".  In there I would assign a unique name to every occurrence (the one in Yellow) for each part.  So, for example, under the Instance (White) for U1A, I would open it up and Assign "Amp1, Amp2..." to the different occurrences (Yellow) within the Circuit Description property that I created.  I did the same for U1B.  Now, the Instance for U1 will have eight unique Occurrences underneath it that will keep the link together for each page.  U1A will have a representation on the Amp1 page as will U1B because you declared them to be unique within that User Property.  The final step is to add {Circuit Description} to the end of the Combined Property String value in the Annotate dialog so that it will consider this property when assigning the RefDes.  This will allow the annotate to perform successfully.

    A couple notes from my experience here:

    • I only had to do this to my ICs as the passives went through OK by themselves.  Almost all of my ICs are Heterogeneous with a separate power section for each one at the minimum, so this definitely exacerbated the problem, I'm sure.
    • You have to take care when you have multiples of the same part on the same page.  Then you have to give them each a unique name in the User Property.
    • If you don't really get the differences between Instances and Occurrences, you need to.  Refer to this article.  It helps.
    • Hopefully it goes without saying, but make sure that you check "Update Occurrences" in the Annotate Dialog

    It took me a while to get to the bottom of this, so I hope that this post helps someone else.  Happy Designing!

  • xiaoyi594

    Hi Jonathan!

    Thanks for sharing! I tried your method and it works! The critical part is "add {Circuit Description} ".

    By the way, the reference link you post "Refer to this article." seems to be unable to access, could you please post the original url ?

    Thanks again. Happy weekends.

    Vid

  • George Dishman

    The words "Refer to this article" are stuck on the end of the URL, try this:

    http://community.cadence.com/cadence_blogs_8/b/pcb/archive/2013/05/02/customer-support-recommended-understanding-instance-and-occurrence-modes-of-design-annotation-using-allegro-design-entry-cis

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.