• 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 Design
  3. Adding Layout block from Encounter to custom design

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15984
  • 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

Adding Layout block from Encounter to custom design

Kabal
Kabal over 11 years ago

I managed to get Encounter auto-route and place the design, imported it into the Virtuoso environment as a Layout view, then runned DRC, then runned LVS versus the CDL file of standard cells and verilog file exported from encounter.

Now, I want to put this layout inside another custom layed out design. Right now, I have one design with some transistors, manually connected in schematic, and manually layed out, so I want to add this layout to that design and put it in a top level block, and then DRC and LVS it.

The way I do manual designs is, I first do schematics by hand in SchematicsXL, then I export the CDL netlist, then I pass it through the LVS script of IBM kit to convert it to LVS suitable format. Then I do layout, and do LVS versus the CDL netlist.

But in this case, I am going to use the layed out and separately LVS'ed Layout I have in another cell. That another cell has only Layout view, and a Symbol view I created for it.

The thing is, once I put that symbol inside a schematic with custom elements, and try to export netlist, the system complains saying that there is no "schematic" view.

In my export window of netlist as a View List there is: auCdl schematic, and as stop view: auCdl.

 My question is: How do I integrate my imported Layout block on a schematics level in my top level block with manually designed stuff around it? Because, there is no "schematic" view in that Layout block, I did its LVS versus the CDL file of standard cells lib and verilog file from encounter.

 I searched and know that people also do something like, import verilog to schematics. But then, my another question is, can I avoid that step? I really do not want to deal with schematics, even though this design is not that big, but I dont want to deal with it during the next very big designs.

Is there a way to export netlist from schematics with symbol of another imported block which only has Layout view without dealing with its schematics? 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Often people do Verilog-In the verilog to produce schematics, but another approach would be to create a copy of the symbol and make it the "auCdl" view, and set up the CDF so that it netlists the auCdl view as an instance of the block (you can specify the termOrder for auCdl in the CDF, which you could probably just auto-create by opening the symbol and running artGenerateHierSymbolCDF(geGetEditCellView()) ).

    Then in Assura you can specify a mixture of CDL and Verilog netlists to LVS against. Note, I've not tried this personally for some time, but I think it should work OK.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Often people do Verilog-In the verilog to produce schematics, but another approach would be to create a copy of the symbol and make it the "auCdl" view, and set up the CDF so that it netlists the auCdl view as an instance of the block (you can specify the termOrder for auCdl in the CDF, which you could probably just auto-create by opening the symbol and running artGenerateHierSymbolCDF(geGetEditCellView()) ).

    Then in Assura you can specify a mixture of CDL and Verilog netlists to LVS against. Note, I've not tried this personally for some time, but I think it should work OK.

    Regards,

    Andrew.

    • 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