Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 9024
  • 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

Layout XL: "Connectivity->Update->Components and Nets" resets all my pins

PNadeau

Dear folks,

Sometimes I make a few schematic changes and then in Layout XL I use Connectivity->Update->Components And Nets to update the Layout connectivity.  I select "Update nets and Instance name mismatches only" and "Update Net Signal Type" and click OK.

When I do this, the tool moves all of the pins I have already placed to the lower left-hand corner of the layout, despite nothing really changing on most of these nets, causing me to have to place them all again.

Is there a way to prevent this behaviour?  Ideally I'd like to leave most of the pins alone if nothing has changed on those nets.

If it's relevant, the pins were initially placed using Connectivity->Generate->Selected From Source, and using the "Unplaced" and "Place Individually" mode.  The pin and label are placed on the "pin" LPP for the relevant metal.

IC6.1.6.101, RHEL 6

Thanks in advance.

Cheers,
Phil

Parents
  • PNadeau

    Hi Colin,

    Thanks.  I tried your suggestion but it didn't quite work.  For me, when I click the "Update Nets and Instance Mismatches Only," most options, including the I/O Pins tab, are greyed out (attached screenshot). I can make the I/O Pins tab active by unselecting "Update Nets..." and Selecting "I/O Pins" in the "Generate" section.  Then I tried:

    1) Unchecking "Create" in the "Specify Default Values", going back and checking the "Update Nets..." (which greys out everything) and running,

    2) Unchecking "Create" and not selecting "Update nets..." (leaves all options still active) and running

    3) Unchecking "Create", going back to "Update" tab and unselecting all options except for "I/O Pins" (to leave the I/O Pins tab active) and running

    All three of these still moved 100 of my pins to the lower left of the layout. I also tried adding the "Locked" constraint to the pins using the constraint manager, but they are still moved by "Update nets..." (and cannot be moved further unless I unlock them).

    Is there another way to update the connectivity without having to re-place all the pins?

    Cheers,

    Phil

Reply
  • PNadeau

    Hi Colin,

    Thanks.  I tried your suggestion but it didn't quite work.  For me, when I click the "Update Nets and Instance Mismatches Only," most options, including the I/O Pins tab, are greyed out (attached screenshot). I can make the I/O Pins tab active by unselecting "Update Nets..." and Selecting "I/O Pins" in the "Generate" section.  Then I tried:

    1) Unchecking "Create" in the "Specify Default Values", going back and checking the "Update Nets..." (which greys out everything) and running,

    2) Unchecking "Create" and not selecting "Update nets..." (leaves all options still active) and running

    3) Unchecking "Create", going back to "Update" tab and unselecting all options except for "I/O Pins" (to leave the I/O Pins tab active) and running

    All three of these still moved 100 of my pins to the lower left of the layout. I also tried adding the "Locked" constraint to the pins using the constraint manager, but they are still moved by "Update nets..." (and cannot be moved further unless I unlock them).

    Is there another way to update the connectivity without having to re-place all the pins?

    Cheers,

    Phil

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.