Stats

  • Locked Locked
  • Replies 3
  • Subscribers 166
  • Views 13933
  • 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

Capture 17.2 S051 automatically assigns xnets

LouShay

Hi All, It appears that Capture 17.2 S051 is automatically assigning xnets to existing schematic. I think this coincides with the introduction of Constraint Manager for Capture. I’m curious if anyone else has recognized this? It can wreak havoc on net-classes already defined in Allegro.  Thanks. 

  • steve

    This is now default behaviour IF you invoke the Constraint Manager flow. You need to add a property NO_XNET_CONNECTION with a value of TRUE to the discrete parts that you don't want an xnet on. 

  • LouShay
    in reply to steve

    Thanks Steve. Seems like Cadence has decided to force Xnets upon your design, when the choice to use Xnets or not should have no relation to the use of Constraint Manager. So I’m left scratching my head why, and a cumbersome step to correct it. I’m open to understanding if someone has an explanation for this. Thanks for your feedback.   

  • redwire
    in reply to LouShay

    It's been this way for a while and it was intended to be helpful.  Like steve says, you have to apply the property and the problem goes away.

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.