Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 13687
  • 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

Issues in shielding

PramodSabnis

 I am facing this peculiar issue while trying to do shielding on clock nets.

 The flow followed is as follows:

- Set attributes on clock nets

- Apply the attribute in clock spec file

 

I also set the following variables:

- setNanoRouteMode -routeDeferredShield true

Router carries out shielding at the end of routing. However, what I see is that this ends with a plenty of "Wire Extension" category of DRCs on ths shield nets (not the shielded ones).

Has anyone seen this behaviour? How do I fix these violations in an automated manner (there are plenty of those so, manual fix is ruled out)?

 

Best regards,

Pramod

Parents
  • Hi Pramod, Do you have access to the latest 8.1.USR3 release? I've been working with a customer recently who reported very similar issues to what you're describing that were resolved in bug fixes just recently. Thanks, Bob
Reply
  • Hi Pramod, Do you have access to the latest 8.1.USR3 release? I've been working with a customer recently who reported very similar issues to what you're describing that were resolved in bug fixes just recently. Thanks, Bob
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.