Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I want to use a nport in Verilog-A/Verilog-AMS. The implementation has been done like this:nport #(.file("/my_folder/my_device.sparam"), .interp("spline"), .thermalnoise("no"), .usewindow("yes")) N0 (BiasN, AVSS, BiasN_cm, AVSS, BiasP, AVSS, CBiasN, AVSS);But when I try to simulate, there's this error that the file can't be found.ERROR (CMI-2011): Unable to open S-parameter file `"/my_folder/my_device.sparam"'.When I copy the path and try to open the file with emacs there's no error. So could someone tell me, where's my error in implementation or usage?
Thanks a lot,Tobias
I suspect it's the way you are defining the path in the file parameter. Try using a full path, rather than relative path.
Also, it's good practice to designate your s-parameter files as mydevicesparam.s3p (or .s2p, .s4p, etc.). Not a big deal, but if you later want to plot those s-parameters in ViVA standalone, you'll be able to do so.
Sr. Staff Support AE, Global Customer Support
Cadence Design Systems, Inc.
In reply to Tawna:
Thanks for your advice. I now tried everything relating the way how to define the path. absolute (starting with /), relative (with ./) and, as the file is in a subdir of my home directory, with a ~/...../ .the solution with the ~/ is correctly substituted with my home path, as the error message points to the correct file.
in my opinion, it is strange that the errormessage quotes the path twice, once with ` and then directly after the first quoting with " and closes then the " quote and the the '.
Has anybody already implemented the nport in verliog-a or verilog-ams? could someone post a code snippet for example?
In reply to TobiasM:
With regards to setting your path, you may want to look at the following Solution:
Note that this is for the n2port...it will be the same for the nport. In fact, you should use "nport" instead of "n2port", "n3port", etc.
There shouldn't be any issues with nport and AMS-D (that I am aware of at this point). You will definitely want to look at the nport appNote, however, to see how to set up parameters (if you don't set it up properly, you may not get the results that you expect).
You can obtain the appNote at
Thanks for your fast replies. I've read now all the documents you mentioned. The Solution described in your first link ("Unable to open S-parameter file during Spectre run if path given is relative path") showed the error message if the file is not found. But in contrast to my error message, the file is only quoted by a ` and ':Unable to open S-parameter file `myspFile.s2p'.While my error message would look like this:Unable to open S-parameter file `"myspFile.s2p"'.
Where could this come from, as I neet to quote the filename when instantiating the nport in Verilog-A?