• 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. Digital Implementation
  3. Power stripes. Got moved. Not touching the boundary edge...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13875
  • 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

Power stripes. Got moved. Not touching the boundary edge. How to catch it.

Ivan de Trble
Ivan de Trble over 13 years ago

Howdy gang,

Got burned having to redo a bunch of work, because at the top level they realized that "some" of my horizontal power stripes where not touching the boundary. You can imagine how pissed (and embarrased I was).

Any of you know of a verification I can run to catch this. 

I do my blocks with a .tcl script. I source it into encounter and I let the block come out like bread out of the oven. So I only check if there are any DRC, LVS, ANT errors, which of course there aren't any, the open is at the next level above me.

However one time I had to go in and manually fix some antenna errors. This is when I believe I touched some of those stripes and moved them by accident.

I appreciate any help.

Ivan

 

  • Cancel
  • Kari
    Kari over 13 years ago

     I'm not sure if the stripes never touched the boundary, or did when you started then got moved somehow later. If they are getting moved, you need to figure out which step in your flow is moving them. If they never touched the boundary in the first place, make sure you're using the power command options to extend to the design boundary. Usually for major power grid stuff, we perform a visual check before handing off data.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ivan de Trble
    Ivan de Trble over 13 years ago

     Hi Cary,

     That's the thing, I had already removed my log directories; had way too many. There were various changes throughout the process of making the block due to timing issues, so I kept going in and out of the encounter sessions. In one of those sessions, I must have touched "some" of the power lines w/o noticing it, and well, you know the rest.

    I WILL from now on keep an eye on them, but would be nice to have something to fall back on. Perhaps inside the verifyConnectivity  -type special command, a warning that the power lines are not touching the boundaries? Or, since asking can't hurt, an option to choose wheather I want them to go all the way out to the IO boundary or the Core boundary (?), and of course, which metals.

    Here is hoping. Or perhaps, do you know how can I submit this request to the Cadence Gods?

     

    Thanks for input. Nice to know someone is out there hearing my cry.

    Ivan

     

     P.S. I forgot to answer your question! Pwr/Gnd horizontal stripes were up to the IO boundary from the very beginning; floorplanning step.

    P.S.2. How do you spell your name? Kari or Cary? Your picture says Cary, and the Cadence automatic message says Kari: " Kari wrote the following post at 01-16-2012 7:37 PM"

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 13 years ago

     Hi Ivan,

     To submit a service request, you can log into your support.cadence.com account and click "Service Requests" along the top.

    If you choose the option to create stripes with a pin at the boundary, and the stripe gets moved away from the pin, then verifyConnectivity will give you an Open error. But if you accidentally delete the pin too, then there is nothing to say that the stripe should have gone to the edge.

     

    BTW, My name is spelled Kari, and the town where I work is called Cary. Yes, it can get confusing especially on phone calls when you don't see the spelling. :-)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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