Stats

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

LayoutXL stop layers

PNadeau

Dear folks,

I am running in to a lot of false shorts in LayoutXL connectivity. Using the LayoutXL Options -> Connectivity -> Diagnostics Report, it seems because my PDK's tech file does not define the stop layers in any of the constraint groups.  

Does anyone know of a reasonably straightforward way of defining a simple stop layer (like diffusion interacting with poly) so that I could get this working on my own?

I am familiar with the Process Rule Override, but I do not see a stop layer option here.  I also see the Incremental Tech DB flow might be an option, but I'm wondering if there is a simpler or better way?

Cheers,

Phil 

  • Andrew Beckett

    So you mean being able to do something like is described in the Virtuoso Layout Suite XL User Guide in the section Specifying Stop Layers in the validLayers Constraint ? It gives an example:

    Consider the following derived layer definitions in the validLayers constraint:

    (StoppedLayer 10001 (Oxide 'not Poly))
    (validLayers (StoppedLayer))

    The "StoppedLayer" is not a constraint - it needs to be defined in the techDerivedLayers section of the layerDefinitions section.

    So if this is what you mean, then Incremental Tech DB is the way to go, I think.

    Regards,

    Andrew.

  • PNadeau

    Hi Andrew,

    Thanks very much. Yes, I did see that note in the guide. Understand now the best way to implement this is through the incremental Tech DB flow.  I'll try jumping in if t's simple enough... thanks!

    Best,

    Phil

  • PNadeau
    Wasn't all that bad actually, for someone who never manipulates tech files....

    For anyone else coming across this, I used CIW->Tools->Technology File Manager. The steps:

    (1) Since my design library was already attached to the PDK tech lib, I found I had to "Attach" cdsDefTechLib so that it would allow me to access my design library in the "Set Reference" window (maybe there is a better way...).

    (2) "Set Reference"on my design library pointing to the original PDK lib (now it is *referenced* instead of *attached*).

    (3) "Dump"ed the tech lib from my design library to ASCII (basically just contains the reference and you can make it generate all the headers)

    (4) Made the edits to the ASCII file, and then "Load"-ed back in.

    All commands in quotes "" refer to Tech. File Manager operations...

    Cheers,
    Phil

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.