Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 16876
  • 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 to pass the file name as a variable to vsource as PWL type

RFStuff

Dear All,

We can directly give the filename in vsource when it is as PWL source type.

Is there a way we can pass the file name as a variable to vsource as PWL type ?

I need to change the file name for different corners.

  • in reply to Andrew Beckett

    Hi Andrew,

    The method described in your link has worked well for me, but we recently moved up to IC6.1.8, which forces the use of the AMS Unified Netlister.  The method doesn't seem to work for that case as I get the following error.  I can easily switch between UNL and OSS-based in IC6.1.7 and go from not working to working with everything else the same.  Any thoughts?

    Warning from spectre in `cds_globals', during circuit read-in.
    WARNING (SFE-2946):
    "/scratch/jp031104/simulation/test_RFFE_Inputs/ams/config/netlist/cds_globals.vams"
    18: `cds_globals': Parameter `myfile' redefines parameter of same name
    defined at higher level. Local parameter value will be used.

    Reading link:
    /apps/cadence/INCISIV/INCISIV152_ISR14/tools.lnx86/spectre/etc/ahdl/discipline.h
    Time for Elaboration: CPU = 22.996 ms, elapsed = 31.194 ms.
    Time accumulated: CPU = 1.41378 s, elapsed = 2.78549 s.
    Peak resident memory used = 105 Mbytes.

    Time for EDB Visiting: CPU = 0 s, elapsed = 231.028 us.
    Time accumulated: CPU = 1.41378 s, elapsed = 2.78584 s.
    Peak resident memory used = 105 Mbytes.


    Error found by spectre during initial setup.
    ERROR (CMI-2011): Unable to open waveform file `cds_globals.myfile'.
    No such file or directory.

  • in reply to oljd

    Apologies for the delay - only just had a chance to check this.

    I've tried it, and this works for me. I'm wondering if there's a step you omitted? I'm not quite sure what could cause these warnings/errors - I'd have to see the data. Since you probably can't share that here, it would probably make sense to raise this with customer support so that we can look at your data. If you do that, it's OK if you point at this post and suggest that I'd be willing to look at the data to try to understand what's wrong.

    Kind Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    I found that using a recent version of Xcelium, instead of Incisive, does the trick and works like it did in IC6.1.7.  Thanks for the response.

    Best regards,

    olJD

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.