Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 14452
  • 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

How could I make my PV GUI communicate with Virtuoso through port so gds export has no issue

mctang

Hi 

I try to use “pipo strmout out.tmpl” in batch mode to export gds, which is invoked by my PV runtime GUI. However, I get the following error

message. Internal virtuoso wrapper script defines environment VARIABLES which cannot be recognized by batch-mode pipo/strmout

 

Reading Cadence database ...

*WARNING* '/mrvl2/tcad10s/pganl4/pganl4/wa/mctang/CALIBRE_SUPPORT/backup/cadence/skill/CODE_EXAMPLE/menu_runtime/workdir/cds.lib', Line 1: Cannot find file '/proj/cdspdk/tsmc/t16nm/CRN16FF+LL_LOGIC/$FOUNDRY_PDK_VERSION/PDK_ic61/1P11M_2Xa1Xd_h_3Xe_vhv_2Y2R/cds.lib'.

*WARNING* '/mrvl2/tcad10s/pganl4/pganl4/wa/mctang/CALIBRE_SUPPORT/backup/cadence/skill/CODE_EXAMPLE/menu_runtime/workdir/cds.lib', Line 1: Skipping: '/proj/cdspdk/tsmc/t16nm/CRN16FF+LL_LOGIC/$FOUNDRY_PDK_VERSION/PDK_ic61/1P11M_2Xa1Xd_h_3Xe_vhv_2Y2R/cds.lib'

FATAL (4): Failed to open the technology file `techfile.cds' from library `test_sch'. Check that the library exists in the location defined in the 'cds.lib' file and that you have read permission to the technology file.

 

I would like to send the command from my PV runtime GUI directly to Virtuoso through port. I could implement this feature in another layout tool.

If I use “FILE-> Export”  from CIW, the following command is executed and  there is no gds export  issue. Could you show me how to implement in Cadence Virtuoso ?

strmout -library 'test_sch' -strmFile 'PLL_A.gds' -techLib 'tsmcN16' -topCell 'PLL_A' -view 'layout' -logFile 'strmOut.log' -enableColoring Virtuoso Framework License (111) was checked out successfully. Total checkout time was 0.05s.

Thanks,

ManChak

  • Andrew Beckett

    I'm not sure why you are trying to run "pipo" - this is an executable for stream out from IC5141. In IC61X releases it is called "strmout". So maybe that's your problem - you're using an old IC5141 (CDB) executable rather than an IC61X (OA) executable?

    I've not seen the "internal" error before and can't find reports of it either. Maybe it's a wrapper script for your company, not a Cadence script?

    Regards,

    Andrew.

  • mctang

    Hi Andrew,

    Thank you for your help. PIPO should not be used for IC61X. I will encounter the same problem if I use "strmout".

    The error message is due to

    envVars in Unix are not evaluated when calling strmout in batch mode. It seems that batch mode strmout does not read .cdsinit and thus the envVar(s) to point to foundry techfile do not get loaded.

    I am currently using "system(strmout xxx   &)" command in my perl script. I am not sure ipc command can fix the above problem (missing environment variable)

    Thanks,

    ManChak

  • Andrew Beckett

    This doesn't make any sense. Sure enough, strmout doesn't read the .cdsinit but I don't see what that has to do with strmout not evaluating envVars - the environment variables would be evaluated by the shell used to invoke the strmout command anyway, so that would work.

    Having seen an internal email, it looks to me as if you're also asking questions via customer support (case 45957207). Please don't ask both in the forums and customer support (unless you're directed to customer support from here) because it just duplicates effort and nobody knows who is doing what.

    So my assumption (consistent with what I've seen by the case in question in the internal discussion) is that this is just you doing something incorrectly and there's really not enough in the thread above to be able to help you out. I suggest you continue working through the case instead.

    Kind Regards,

    Andrew,

  • mctang

    Hi Andrew,

    Thank you for your info. I found out that  ipcSkillProcess preserves all environment variables which could  fix strmout issue due to $FOUNDRY_PDK_VERSION in.cslib. I will continue working through the case to resolve the remaining problems.

    Thanks,

    ManChak

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.