Stats

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

How to get all blocking layers touching a Pcell from inside Pcell code

sfiswoo

Hi

I am writting a Pcell and want to avoid adding metal under routing blockages. The routing blockages are at the same hierarchy as the Pcell, and are not generated "inside" the pcell. I am having a hard time figuring out how to get the regions of the pcell that overlap any routing blockages. Here is how I am approaching the issue:

  1. cv = dbOpenCellViewByType( libName CellName ViewName "maskLayout" "r") ; Open the level that contains both the pcell and the blockage
  2. PGInst = dbFindAnyInstByName(cv PCELLNAME)
  3. dbLayerBlockageQuery(cv "M1" PGInst ~>bBox 0 0)
  4. Do some other stuff.

The issue is not sure how to get the name of the Pell from inside the Pcell code. Any ideas? Or maybe I should be approaching this a different way?

Cheers

  • This is not a safe thing to do with PCells, as the evaluation of the PCell is not per-instance, but is per-variant. That means that if you have four instances of the PCell in the same or different cellViews with the same parameters, the PCell code will be evaluated once only - for whichever instance happened to trigger it first. Consequently you can't find the instance name of the instantiation nor (reliable) information about where it is instantiated (because it will depend on whether all instantiations have been opened yet, which is unlikely if the code is being triggered).

    So doing this within the PCell is not supported.

    Andrew

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.