Stats

  • Locked Locked
  • Replies 12
  • Subscribers 126
  • Views 6879
  • 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

automating schematic to post layout simulation flow

supriyo1985

Hi, 

I need some help automating a flow that takes a schematic as input, calls the automatic placer and router in Layout Suite GXL, extracts parasitics using Calibre PEX, and then runs a post-layout simulation.

I was planning to use Ocean Script for this purpose. I noticed that when I executed the above steps manually through GUI, all the commands and outputs were printed on the Virtuoso main window. For example, the automatic router invoked the following commands and several others.

**************************************************************

*                                                            *

*    Begin Min-Spanning-Tree Routing Flow for Normal Nets    *

*                                                            *

**************************************************************

REPORTING_STATS | Elapsed Time: 0.0 Secs | Mem: "Current: 2369.00" Mb | Cmd: initialize_partition -set sel:4654ce30

[::ia:: INFO] Sourcing /usr/local/packages/cadence_2021/IC618/share/cdssetup/dfII/ia/tcl/checkRoutability/flow.tcl

**************************************************************

*                                                            *

*    Begin Check Routability Flow                            *

*                                                            *

**************************************************************

route_optimize -set sel:4fda8f80 -route_over_pins true -truncate_at_pins false -allow_wrongway true -make_only_net_spec_vias true -uniform_taper_to_first_via true

However, when I manually executed the above command, the tool failed to recognize it.

*Error* eval: undefined function - route_optimize. 

How do I go about this problem? Could anybody help? I have attached a figure so that it is easy to understand what I am doing. 

Regards

Supriyo

  • in reply to supriyo1985

    I was able to get around the nclAnalogAutoPlaceCB issue. Basically, I deleted the old PR boundary, created a larger boundary and set the lower left corner to (0,0), moved the cells inside the boundary, and then did nclAnalogAutoPlaceCB a couple of times. 

    I have updated step 2 in Google Docs for reference. 

    I now have an automated flow that can run from schematic to PEX. Thanks for help. 

    I am having some problems running the ocean script inside CIW but I am working on it. 

  • in reply to supriyo1985

    One finding, 

    it seems nclAnalogAutoPlaceCB works if I use gpe* cmds for modgen creation. I think ciConCreate has some issues. 

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.