Stats

  • Locked Locked
  • Replies 7
  • Subscribers 62
  • Views 15849
  • 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

Running VPCD from command line?

tkhan

Hi,

Since the menu option for VPCD has been removed in IC614, I want to use VPCD from command line but I can not generate a cell which I have synthesized. When running from the dropdown menu in IC, the Configuration option lets you choose which library the generated cell is created in (_psmsChooseLibForm->_psmsLibNameStrField->value = "lab2" is what shows up in virtuoso), how can I set this via the command line? vpcd -h does not give any clue, nor do the files in ~/.vpcm_datdir.

Thanks,

Tarek

Parents

  • For anyone who's interested, it looks like inductors generated by VPCD can't be used with MMSIM72 (pehaps with some environment tweaking it could).

    \o VPCD ERROR: Failed to load context file for VPCDLikely Cause: The current version of MMSIM does not support VPCDWARNING: The VPCD-synthesized layout structures will not bedrawn correctly without this context file.Loading schematic.cxt 

    Opening a PCD layout yields "pcellEvalFailed", I didn't try the layout_flat view though.

    \e <<< Stack Trace >>>
    \e strcat(getShellEnvVar("CDS_VPCD_HOME") "/etc/context/VPCM.cxt")
    \e loadContext(strcat(getShellEnvVar("CDS_VPCD_HOME") "/etc/context/VPCM.cxt"))
    \e ...
    \e *Error* eval: undefined function - _pmms_loadModelFile
    \e <<< Stack Trace >>>
    \e _pmms_loadModelFile()
    \e loadi("/blah/blah/blah/libInit.il")
    \e ...
    \w *WARNING* (DB-270001): Pcell evaluation for vpcm/PCM_sym_oct/layout has the following error(s):
    \w *WARNING* (DB-270002): ("eval" 0 t nil ("*Error* eval: undefined function" _pmms_sym_Wrapper))
    \w *WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.
    \w *WARNING* (DB-270001): Pcell evaluation for vpcm/PCM_shld_oct/layout has the following error(s):
    \w *WARNING* (DB-270002): ("eval" 0 t nil ("*Error* eval: undefined function" _pmms_shld_oct_Wrapper))
    \w *WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.

    I suppose I could set CDS_VPCD_HOME to <MMSIM71_HOME>/tools/vpcd, but mixing MMSIM71 and MMSIM72 doesn't seem like a good idea.

Reply

  • For anyone who's interested, it looks like inductors generated by VPCD can't be used with MMSIM72 (pehaps with some environment tweaking it could).

    \o VPCD ERROR: Failed to load context file for VPCDLikely Cause: The current version of MMSIM does not support VPCDWARNING: The VPCD-synthesized layout structures will not bedrawn correctly without this context file.Loading schematic.cxt 

    Opening a PCD layout yields "pcellEvalFailed", I didn't try the layout_flat view though.

    \e <<< Stack Trace >>>
    \e strcat(getShellEnvVar("CDS_VPCD_HOME") "/etc/context/VPCM.cxt")
    \e loadContext(strcat(getShellEnvVar("CDS_VPCD_HOME") "/etc/context/VPCM.cxt"))
    \e ...
    \e *Error* eval: undefined function - _pmms_loadModelFile
    \e <<< Stack Trace >>>
    \e _pmms_loadModelFile()
    \e loadi("/blah/blah/blah/libInit.il")
    \e ...
    \w *WARNING* (DB-270001): Pcell evaluation for vpcm/PCM_sym_oct/layout has the following error(s):
    \w *WARNING* (DB-270002): ("eval" 0 t nil ("*Error* eval: undefined function" _pmms_sym_Wrapper))
    \w *WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.
    \w *WARNING* (DB-270001): Pcell evaluation for vpcm/PCM_shld_oct/layout has the following error(s):
    \w *WARNING* (DB-270002): ("eval" 0 t nil ("*Error* eval: undefined function" _pmms_shld_oct_Wrapper))
    \w *WARNING* (DB-270003): Error kept in "errorDesc" property of the label "pcellEvalFailed" on layer/purpose "marker/error" in the submaster.

    I suppose I could set CDS_VPCD_HOME to <MMSIM71_HOME>/tools/vpcd, but mixing MMSIM71 and MMSIM72 doesn't seem like a good idea.

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.