Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 11380
  • 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

Can I generate layout from source but not from the same hierarchy level?

delgsy

Let's say I have this hierarchy in the schematic:
TOP
|--I1
|   |--M1, M2, I3
|
|--I2
    |--M1, M2, M3, I4

So, I1 and I2 are on the same hierarchy level.

I do not want to create the layout of I1 and I2.
what I want is creating the layout of TOP by instantiating M1, M2, I3 from I1 and M1, M2, M3, I4 from I2.
Is it possible?
if yes, how to manage the hierarchy so it pass the LVS.

In TOP layout, I am aware I can instantiate any cell layout, but I am not sure how to manage the hierarchy and how to instantiate devices, e.g., M, R, C.

Parents
  • Changyou Fan

    Yes you can achieve that by following these steps:

    1. In layout window, Launch->Configure Physical Hierarchy 

    2. In the pop-up form, select "Hierarchy Configuration" (by default), In the tab of "instances", click on I1

    3. RMB->set/remove force descend

    4. Do the same to I2.

    5. Save and quit this form

    6. Run Generate From Source

  • Andrew Beckett
    in reply to Changyou Fan

    In addition to Changyou's useful advice, those steps should only be needed if the layout already exists for the cells for I1 and I2. If there's no layout existing already, then it would flatten the hierarchy anyway during layout generation.

    I wouldn't expect that to cause any issue with LVS; LVS usually would handle that automatically.

    Andrew

Reply
  • Andrew Beckett
    in reply to Changyou Fan

    In addition to Changyou's useful advice, those steps should only be needed if the layout already exists for the cells for I1 and I2. If there's no layout existing already, then it would flatten the hierarchy anyway during layout generation.

    I wouldn't expect that to cause any issue with LVS; LVS usually would handle that automatically.

    Andrew

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.