Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14491
  • 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

Converting a veriloga model to a schematic symbol

lbodepu

Hi ,

I am using a code which is very similar to the schematic to the symbol

procedure(CCSautoCreateSymbol(sourceLib reCreate)
let((libId targetLib cellList sourceView targetView dataTypeView funct1 funct2)

libId = ddGetObj(sourceLib)
targetLib = sourceLib
cellList = libId~>cells
sourceView = "veriloga"
targetView = "symbol"
dataTypeView="schematicSymbol"


foreach(cell cellList
if(member(sourceView cell~>views~>name) then
if( reCreate || !member("symbol" cell~>views~>name) then


schHiViewToView(?libName sourceLib     ?cellName cell~>name      ?viewNameFrom sourceView         ?viewNameTo targetView    ?dataType dataTypeView )

) ;if
) ;if
);foreach
ddReleaseObj(libId)
);let

printf("\nJob Done!\n")
);procedure

But I am not able to automatically close the dialog box Cellview from Cellview.

Is there any command that I have to add to automate it?

Regards,

Lavanya 

  • Andrew Beckett

    Hi Lavanya,

    I suggest you use schViewToView rather than schHiViewToView (see the documentation for the usage details). This then does not bring up a form.

    Regards,

    Andrew.

  • lbodepu
    in reply to Andrew Beckett

    Hi Andrew,

    I am not able to use schViewToView because its arguments schVerilogToPinList doesnt seem to work for verilog a.

    Lavanya

  • Andrew Beckett
    in reply to lbodepu

    Hi Lavanya,

    You need to use ahdlToPinList instead of schVerilogToPinList. Or for generating VerilogA from a pin list you'd use ahdlPinListToveriloga . Not sure why these aren't documented (they should be). This article helps you find the relevant functions: schViewToView: How to find translation functions for different views

    Andrew.

  • lbodepu
    in reply to Andrew Beckett

    Thank you for the help 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.