-
Notifications
You must be signed in to change notification settings - Fork 72
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
Argument on Xcelium build forces pre-step setup #127
Comments
As far as I understand I have split the run on elaboration/compilation and execution. I still would like to use
This is I do not understand? Why if would not work? |
Let me re-write that sentence, the same test that works fine with standard makefile flow (without Cocotb-test) on Xcelium/Ius doesn't work when running through cocotb-test/pytest bc of this issue with the simulator: INFO cocotb:simulator.py:255 define XMSIMRC ( /mnt/simvision/tools/xcelium/files/xmsimrc, ~/.xmsimrc )
INFO cocotb:simulator.py:255 |
INFO cocotb:simulator.py:255 xrun: *F,DLHVAR (./xcelium.d/run.lnx8664.18.03.d/hdl.var,1): hdl.var invalid variable '~ == $HOME'.
ERROR cocotb:simulator.py:258 Command terminated with error 2 |
Did you run in the same directory I cannot reproduce this. |
Hey @themperek, I followed these steps but I'm still seeing the issues, I'm attaching the two logs, one with the run through tox (Cocotb-test) and another one with Makefile, I'm attaching the sim_build folders, obviously the one with tox is considering just one of the parameters in the test but it works pretty much in the same manner. Would you mind to take a look and let me know what's the difference between the two executions? One of the things I noticed is that in the makefile run, there's the $TOP folder created under /worklib what's not present in the Cocotb-test run (tox/pytest). I consider that my setup with tox is correct bc with Verilator I can run with no issues the test, although when I switch the simulator to be xcelium then I see the problems. |
Is the same happening on any example? Like |
You can also https://github.com/themperek/cocotb-test/blob/master/tests/test_dff_custom_sim.py (I have to improve this example). |
I had the same error with tests/test_dff.py, actually if I copy the command that fails when running with pytest and paste in the terminal to execute, it works like a charm....I really don't understand why the same xrun command when launched by pytest/cocotb-test fails to run |
If I add to tox.ini setenv this: I see another error: -.--ns ERROR cocotb.gpi ..s/cocotb_utils.cpp:69 in utils_dyn_open Unable to open lib cocotbvhpi_ius: cocotbvhpi_ius: cannot open shared object file: No such file or directory
INFO cocotb:simulator.py:255 cocotb: Error loading shared library cocotbvhpi_ius I'm start thinking that's related to the way the pytest call the test... |
What might give a clue is exporting/extending the environment variable |
This is an error if you are using cocotb 1.5 (there ware some changes). In this case, you need to use this #128 I will realise when cocotb release. |
Hi @themperek ERROR: Cannot install cocotb 1.5.0rc2.dev1+gbd98f994 (from git+https://github.com/cocotb/cocotb.git@stable/1.5#egg:cocotb) and cocotb-test==0.1.2.dev0 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested cocotb 1.5.0rc2.dev1+gbd98f994 (from git+https://github.com/cocotb/cocotb.git@stable/1.5#egg:cocotb)
cocotb-test 0.1.2.dev0 depends on cocotb>=1.5 |
Maybe this: https://stackoverflow.com/questions/12759761/python-pip-force-install-ignoring-dependencies Seems |
Apparently it does not...I forked cocotb-test and did some changes to make it work, although I cannot run bc I see now issues with licenses once multiple instances are dispatched, even with tox -- -n 1. |
Hi,
could you please remove the default argument "-elaborate" on Xcelium/Ius simulator, to use that you need to force work lib creation previously, what doesn't happen at time 0 when you're running the sims and by default xrun will know what to call first depending the stage you're. I was wondering why I couldn't run the same tests with cocotb-test that I successfully run with standard makefile flow and removing this argument made it work.
cocotb-test/cocotb_test/simulator.py
Line 607 in 3ed5aac
The text was updated successfully, but these errors were encountered: