Create/Import Verilog-AMS Cell View

I have a problem to import or create a VERILOG-AMS file.

I have to import a device model which has been developed in Verilog-AMS (I have a file with ".vams" extension).
In the following, I try to summarize and explain what I have done and tried.

1) I tried to import my file through the "IMPORT" tool of CADENCE but it seems to be impossible. I have this error: "The parser ncvlog failed to parse the text file. Refer to the file 'ncvlog.log' for compilation messages and errors". I don't know if the problem is related to the verilog editor/compiler named "ncvlog".

2) I tried to use the tool "NC-VERILOG". Also in this case, when I try to generate the netlist from the "verilog-ams" file, I have the following error:"ERROR (OSSHNL-103): Unable to open the design, library 'GMR_Model', cell 'Test_2', view 'verilogams'. Ensure that the cell view exists or the SKILL variable, simDcmFilePath, is correctly defined".

3) I tried to generate a new cell view creating a "Verilog-AMS" file with the "modelwriter" of Cadence or creating a "VerilogAMSText" utilizing a Verilog-AMS editor of Cadence.
Once again I have problems because, in the first case, the ModelWriter of Cadence works fine but it is possible to create "verilog-ams" files only starting from a list of examples, without any possibility to change something. The generated example can be simulated with good results. On the contrary, when I try to generate a new "VerilogAMSText" utilizing a Verilog-AMS editor, a file "verilog-ams" is created, but not opened automatically with the editor. I have this warning: *WARNING* editFile: sh: xterm: command not found.

I tried to set (manually) the editor for "verilog-ams" utilizing this command: "editor=<PATH of the editor>". I checked both "EXTERM" and "ncvlog". In the first case, setting: editor="/ic_tools/cds/IC.6.15.011/tools.lnx86/dracula/bin/32bit/EXTERM", when I try to generate a new file, the window of editor does not appears (probably the Editor doesn't work) and I have this error:/ic_tools/cds/IC.6.15.011/tools.lnx86/dracula/bin/32bit/EXTERM: error while loading shared libraries: libgdbm.so.2: cannot open shared object file: No such file or directory. In the second case, setting: editor="/ic_tools/cds/IC.6.15.011/tools.lnx86/inca/bin/ncvlog", when I try to generate a new file, the window of editor does not appears (probably the Editor doesn't work) and I have no errors. However, in both cases, a file "verilog-ams" is created in the "view" column and it is only possible to open it in "read-only" modality. In this case, the file is opened through a windows of VerilogAMS-Editor without any possibility to modify/edit the file and run the compiler VerilogAMS.

Where is the problem? Is it related to Linux, the installation of CADENCE or other?

First of all, you didn't read the forum guidelines, which tell you not to post in more than one forum. Secondly, your problems appear to be far beyond what you tried above. There appears to be quite a bit of clutching at straws going on!

Some quick answers:

1. There is no "IMPORT" tool for Verilog-AMS . There is File->Import->Verilog which is for importing pure digital (not AMS) verilog. So that won't help you.
2. I don't know what you mean that you tried to use the tool "NC-VERILOG". Presumably Tools->NC Verilog, which is a simulation environment for simulating schematics (and textual verilog views) in ncverilog. This assumes that everything is pure digital verilog (no AMS) and is not an import tool anyway, so this won't help you.
3. Using modelwriter makes no sense, because that is to create models from a UI with a template and so on.
4. You should use File->New->CellView, with the Type set to "VerilogAMSText" and Open with set to "Verilog-AMS". However, this was failing, because it couldn't find "xterm". This is almost certainly because the editor variable is set to the default, "vi". When "vi" is used, it automatically runs "xterm -e vi" - because vi in itself wouldn't open a window. It is rather odd that you do not have xterm in your path, given that this is normally in /usr/bin/xterm - and /usr/bin would normally be in your UNIX path.
5. I have no idea what possessed you to put a Dracula executable called "EXTERM" as the editor variable. Dracula is a physical verification tool, and this is a sub-executable of Dracula. It isn't called "xterm" and anyway, it's not an editor. Simularly setting the editor to "ncvlog" makes no sense since it is not an editor.
6. Try setting editor="nedit" or editor="gedit" or indeed whatever editor you normally use in Linux.

Regards,

Andrew.

Dear Andrew,

firstly, I regret to have posted my problem more than one in the Forum.
Then, I would like to thank you for the help and support.
Now everything is working well.
I can create VerilogA and VerilogAMS views utilizing File->New->CellView, with the Type set to "VerilogA" and "VerilogAMSText", respectively, and employing the default editor for both types. Automatically a symbol view is also created.
Regarding "xterm", I had to find it in the web and install the package. This editor was not present in the specified UNIX path (/usr/bin/).
Then I had to add another PATH (in bashrc) for "ncvlog".
I tried also to set editor="gedit"...much better than "xterm"!!!
Finally, I created a config view of my test-bench cell, setting "spectre" as template.
Simulation results are perfect.

Thank you very much again.

Best regards,
Andrea (Bayes).

BTW, xterm is not an "editor". It's a terminal window.

Anyway, glad you've got it working now.

Regards,

Andrew.