Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 18369
  • 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

Switch View List in Virtuoso CDL Out ignored?

drdanmc

I was trying to export a CDL netlist from virtuoso (IC617) with File->Export->CDL in the CIW.  In the "Virtuoso CDL Out" form, I filled out the "Switch View List" field with "auCdl schematic cmos_sch" (by adding cmos_sch to the end).  However, when I hit apply, the netlisting fails and the error is

ERROR (OSSHNL-116): Unable to descend into any of the views defined in the view list, 'auCdl schematic', for the
instance 'I3' in cell 'MYCELL'. Add one of these views to the cell 'MYSTDCELL' in the
library 'MYSTDCELL_LIB', or modify the view list so that it contains an existing view.

(cell/lib name changed)

So, what gives?  The view list in the error is not the view list I put in the form.   When I looked at the si.env file which got created, I see:

simViewList = '("auCdl" "schematic" "cmos_sch")
simStopList = '("auCdl")

if I manually edit this file and add

cdlSimStopList = '( "auCdl" )
cdlSimViewList = '( "auCdl" "schematic" "cmos_sch")

and run

si -batch -command netlist

from the command line I'm able to netlist.  I do not have a .simrc file anywhere that I can find which might be messing with things.

Any thoughts?

Thanks

-Dan

  • Andrew Beckett

    Hi Dan,

    I just looked into this. The behaviour is clearly wrong, but despite some earlier CCRs, this hasn't been fixed. I have no idea why somebody couldn't actually fix it properly - no point putting fields on the forms if they don't work.

    There's even an article describing that it works this way and that this is expected (it's not expected by me).

    The workaround is to turn off the background mode on the form, and then it will netlist OK and honour the switch and stop view lists. 

    I'm going to create a case on your behalf and file a CCR to push to get this fixed properly.

    Regards,

    Andrew.

  • ricez
    in reply to Andrew Beckett

    I'm having a similar problem.  I'm using 6.1.7-64b.  Trying to netlist a block which contains standard cells which have both a schematic view and an auCdl view.  I don't want to point to the .cdl file for these cells, just want a single netlist, so I think I should be able to place "schematic" in front of "auCdl" in the view list and the netlist would be correct, but it seems the issue runs deeper. 

    I've tried the above from the gui, and also from the command line to no avail. 

    For grins, In the si.env I have in the directory i'm using for command line netlisting, I've changed it to:

    simViewList ='("nothings" "foos" "wtfs")

    simStopList = '("foos")

    and I still get the same netlist.  In the GUI I put in "junkers" "clunkers" into the view list and "unicorns" in the stop list, and still get the same netlist, and the si.env file in the working directory does not reflect my selections, it still has the standard "auCdl", "cdl_sch"....view list and stop list  This happens whether or not the run in background switch is set.

    I also tried adding the cdlsimViewList and stop lists to no avail. 

    ***  Update  ****

    It seems that the only way I can actually control the view/stop lists that are used when netlisting is to create a config view.  If I create a config view for this cell, put the view and stop lists the way I want and then from the command line export the config view, I get the netlist I want.  It's worth noting that the si.env file I have calling out the top level cell and view still has the "nothings" foos and wtf's for a view and stop list

  • Andrew Beckett
    in reply to ricez

    After I filed a CCR for this, it was fixed in IC6.1.7 ISR20 (so IC6.1.7-64b.500.20) - so you should download the latest hotfix from downloads.cadence.com. The config approach  you've used will also work - in which case the view list and stop list are ignored as the config contains all of the view switching information.

    Regards,

    Andrew.

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.