Stats

  • Locked Locked
  • Replies 6
  • Subscribers 142
  • Views 15342
  • 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

Converting a existing library to PCELL library

RK56

Hi,

I have a library of 500+ cells with schematic, symbol and layout views. Now we have decided to create another variant which differs only by single layer (VT variants). So instead of creating another set of 500+ cells I'm looking for an option to convert the existing views to PCELL views and provide an option to chose the Vt.

I have good experience in writing SKILL scripts but I have not tried anything related to PCELLs. So kindly provide me some directions.

Thank you

Ramakrishnan

Parents

  • Thanks Andrew. I'm working on the layout part now. I planned  to implement the schematic as you mentioned. On the symbol, I just need to write a label about the Vt being used and I can figure it myself.

    We used to maintain extracted views (av_extracted) for the standard cells in each cell. Now the question is how to achieve that? I'm totally blank here. What would be the best practice? The parasitics will not change with respect to the transistor VT so does back annotating the caps in schematic is a good idea?

    I'm need help here.

    Thanks

    Ramakrishnan

Reply

  • Thanks Andrew. I'm working on the layout part now. I planned  to implement the schematic as you mentioned. On the symbol, I just need to write a label about the Vt being used and I can figure it myself.

    We used to maintain extracted views (av_extracted) for the standard cells in each cell. Now the question is how to achieve that? I'm totally blank here. What would be the best practice? The parasitics will not change with respect to the transistor VT so does back annotating the caps in schematic is a good idea?

    I'm need help here.

    Thanks

    Ramakrishnan

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.