-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage of Verilog-A modules in subckt's #356
Comments
The procedure of Verilog-A model usage could be found here: https://mos-ak.org/venice_2014/publications/T_4_Brinson_MOS-AK_Venice_2014.pdf The OSDI files are produced with Project->Build Verilog-A module. The version 2.0.0 has the bug related to Verilog-A devices simulation #321 It is fixed in v2.1.0 I didn't check the case when Verilog-A devices are used inside subcircuits. But it should be no difference. Sorry, we have no better documentation for Verilog-A related features. |
You can also specify the |
My version is 2.1.0 build from github 1 week ago. |
There is no explicit device/command in Qucs-S to specify the OSDI file load. The netlist builder scans the schematic and adds the |
It's need to move OSDI files search to |
I have added a fix for this issue. Check the latest commit on the |
I removed the former inserted spiceint cmd's and made a new load va-module and it works perfect. |
I try to reproduce and understand the approach of qucs-s and Verolog-A models in the Verilog-A_EKV_2v6_prj project.
All the examples with flat netlists are working well e.g. the inverter in dc or tran simulation. But start the simulation with the hierarchical netlist (main circuit call's inverter subckt) follow in failure
Error on line:
n.xsub1.nekv26pmos1 out in _net0 _net0 xsub1:mod_ekv26pmos_ekv26pmos1
could not find a valid modelname
Simulation interrupted due to error!
The reason is that the pre_osdi load commands are not inserted into the netlist. This is done for all flat netlists. So the question is by which operation the pre_osdi lines are inserted? Is it "Project/Load Verilog-A module..."? I made this but w/o success.
The text was updated successfully, but these errors were encountered: