• 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. Custom IC Design
  3. Synchronous copy of group with MPP results in flattened...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 15168
  • Members are here 0
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

Synchronous copy of group with MPP results in flattened MPP?

RVERP
RVERP over 8 years ago

I have a strange problem when I copy a mpp within a group. After the copy I end up with the original MPP but also a flattened version with only the subparts.

I perform following steps:

  1. Create 2 new mpp and group them together.
  2. Make a synchronous copy of this group.
  3. Result:
    1. The original MPPs
    2. A flattened version of each MPP, without the main path (subparts only).

This is specially a problem if you want to use synchronous copy. The copied group is not the same as the original and is removed from the clone family.

Selecting 2 MPPs and make a synchronous copy directly has the correct result. However, copying one of the resulting clone family members has the same problem as described above.

The CDS version I use is IC6.1.7-64b.500.4

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I reproduced this, and the problem is still there in IC617 ISR8. If you don't create the group in the first place (i.e. just create a synchronous clone from two MPPs) then it behaves properly - the MPPs are preserved and the clones are synchronised.

    I did a bit of searching and found CCR 1617318 which is for this. There is not yet a plan to fix this (because there's a workaround - below).

    I also notice that when you create the copy, there's a popup "INFO (LX-1361): Family 'Group0' has been removed by cloning consistency check".

    There is a workaround (this is in the CCR, and I've tried it - everything behaved properly after trying this):

    Once the copy is done, you can do the following to resynchronize the clones:

    1. open the Update Clone Families form (Connectivity->Update->Clone Families..)
    2. expand the form by clicking "Create/Add To Family>>" button
    3. select the two "basic" figGroups in the "Layout groups" list (you may need to use the navigator beforehand to identify the groups you want), and which is the "master".
    4. click "Create Family" button.

    => the clones are "resynchronized"

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I reproduced this, and the problem is still there in IC617 ISR8. If you don't create the group in the first place (i.e. just create a synchronous clone from two MPPs) then it behaves properly - the MPPs are preserved and the clones are synchronised.

    I did a bit of searching and found CCR 1617318 which is for this. There is not yet a plan to fix this (because there's a workaround - below).

    I also notice that when you create the copy, there's a popup "INFO (LX-1361): Family 'Group0' has been removed by cloning consistency check".

    There is a workaround (this is in the CCR, and I've tried it - everything behaved properly after trying this):

    Once the copy is done, you can do the following to resynchronize the clones:

    1. open the Update Clone Families form (Connectivity->Update->Clone Families..)
    2. expand the form by clicking "Create/Add To Family>>" button
    3. select the two "basic" figGroups in the "Layout groups" list (you may need to use the navigator beforehand to identify the groups you want), and which is the "master".
    4. click "Create Family" button.

    => the clones are "resynchronized"

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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