• 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. Custom IC SKILL
  3. The geometrical size of the cells bigger then size of device...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 6294
  • 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

The geometrical size of the cells bigger then size of device in my extracted view

TiNat
TiNat over 15 years ago
Hello, I have two technology libraries similar each other. At the first library the geometrical size of the cell at extracted view like the geometrical size of the extracted device (look at fig.1 and fig.2 at attached file). At the second library the geometrical size of the cell at extracted view bigger the geometrical size of the extracted device (look at fig.3 and fig.4 at attached file). I don't understand why this situation has occurred. I copied extract rules and auLvs view of element from the first library to the second. After that I had the same result. Who can help me? When geometrical size of the cell at extracted view bigger the geometrical size of the extracted device, it is not error in IC design but it is uncomfortable because cells are overlap each other. Thank you for your solution.
screen-shots.zip
  • Cancel
Parents
  • Quek
    Quek over 14 years ago

    Hi TiNat

    Just as what you have written, it does not matter that the outlines of the symbol of the cells in the extracted view overlap each other. When a netlister reads an extracted view, only the net connectivity info in the extracted view matters. Regardless of the size of the extracted view, you will be able to get a correct netlist. You can reduce the size of the cells for the 2nd tech library as follows:

    a. Create a text file "myFile" with the following contents
    myTechLib2 cell1 symbol auLvs 15
    myTechLib2 cell2 symbol auLvs 15
    ...

    The above means "magnify the symbol view by 15 times and copy it as a auLvs view".

    b. Enter the following in ciw:
    ivCreatePCells("myFile")

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Quek
    Quek over 14 years ago

    Hi TiNat

    Just as what you have written, it does not matter that the outlines of the symbol of the cells in the extracted view overlap each other. When a netlister reads an extracted view, only the net connectivity info in the extracted view matters. Regardless of the size of the extracted view, you will be able to get a correct netlist. You can reduce the size of the cells for the 2nd tech library as follows:

    a. Create a text file "myFile" with the following contents
    myTechLib2 cell1 symbol auLvs 15
    myTechLib2 cell2 symbol auLvs 15
    ...

    The above means "magnify the symbol view by 15 times and copy it as a auLvs view".

    b. Enter the following in ciw:
    ivCreatePCells("myFile")

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information