Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

First steps using VUnit

797 views
Skip to first unread message

Tobias Baumann

unread,
Jul 4, 2015, 7:23:29 PM7/4/15
to
Hello,

in the last few weeks I read much about VUnit and so I wanted to make
some experiences. I cloned VUnit form Github and tried to run the
example "tb_example".

But when running the run.py script, using "python run.py -v
lib.tb_example*", I get the following error message:

Traceback (most recent call last):
File "run.py", line 2, in <module>
from vunit import VUnit
ImportError: No module named vunit

I tried to add the vunit path to PYTHONPATH enviroment, but this also
gives me the same error message. I'm using Python 2.7.5 but I'm an
absolutly noob (this is the first time, I ever have called python in my
console ;)).

So can someone give me a hint what I'm doing wrong? I read the
user_guide.md on Github page a several times, but I can't find the
missing information I need to get the example running.

Thanks a lot,
Tobias

Lars Asplund

unread,
Jul 5, 2015, 3:21:30 AM7/5/15
to
Hi Tobias,

What is your PYTHONPATH pointing to? It should point to the top directory in which you have the vunit, vhdl, examples directories and not to the vunit directory one level down.

Regards,

Lars

Tobias Baumann

unread,
Jul 5, 2015, 5:03:38 AM7/5/15
to
Hey Lars,

thanks a lot, it is working now. I tried everything except your solution.

Maybe you can add this information to the user_guide.md, then it's clear
for Python noobs how to get VUnit starting.

Best regards,
Tobias

Lars Asplund

unread,
Jul 5, 2015, 8:34:05 AM7/5/15
to
Hi Tobias,

I made an addition to the user guide to make this clear. Thanks for pointing that out. Don't hesitate to get back with more questions if you have trouble with Python. Most VHDL developers have no Python experience so it's important that our documentation covers the basics to get started. Once you're up and running you really don't need that much Python skills. Making basic run scripts is a copy/paste exercise from the given examples.

Best Regards,
Lars

Tobias Baumann

unread,
Jul 6, 2015, 4:27:15 AM7/6/15
to
Hi Lars,

thanks a lot for updating the user guide. I think it contains every
information which is needed to get a first example running.

Now I'm at the point where I have a Jenkins Server which run the VUnit
regression tests on every commit. After the run I can see the JUnit
reports, so I think the beginning is done. The next step will be to run
a multiple regression test of a huge design.

I also saw on the Github page, that there is a discussion how VUnit can
be integrated better into Sigasi. When this also works smoothly, I will
setup a CI server in our firm.

Best regards,
Tobias

Lars Asplund

unread,
Jul 6, 2015, 9:18:44 AM7/6/15
to
Hi Tobias,

Seems like you have very good progress!

You say that you have a huge design to test. Does this means that test time is an issue for you? You might have seen the -p option that allow you to run test cases in parallel on several cores. There are also discussions with other VUnit users to do load balancing between slaves using Jenkins plugins.

Btw, do you have ideas for what you want from a Sigasi integration? If so, please join the discussion here https://github.com/LarsAsplund/vunit/issues/18.

Best Regards,
Lars

Tobias Baumann

unread,
Jul 6, 2015, 10:59:17 AM7/6/15
to
Hi Lars,

> Seems like you have very good progress!
>

Yes, I'm a bit suprised that everything went so fast ;)

> You say that you have a huge design to test. Does this means that test time is an issue for you? You might have seen the -p option that allow you to run test cases in parallel on several cores. There are also discussions with other VUnit users to do load balancing between slaves using Jenkins plugins.

Yes test time is absolutly an issue, but this depends on my IPs. These
are mainly for video algorithm and thereore I have to simulate a
complete frame, which can't parallelize effectivly. But I can try to run
the same IP using different regression setups in parallel. I have to
find out if this is possible with my Modelsim license. If I remember
correctly there can only run one Modelsim instance at the same time.

> Btw, do you have ideas for what you want from a Sigasi integration? If so, please join the discussion here https://github.com/LarsAsplund/vunit/issues/18.

I think what Phillipe mentioned is the right way. For me as Sigasi user,
this means I would have to drag the VUnit folder into eclipse,
right-click on the needed VHDL source files (i.e. vunit/vhdl/200x) and
set them as library vunit_lib. Two clicks and VUnit is ready to use with
Sigasi. Now I have to choose the correct VUnit files for "linking" in
the right library, which is pretty annoying.

Maybe when I'm a bit more in this topic I can give you some suggestions
for improvements. The guys from Sigasi seem to me also very interested
in improving their software. The fusion of both can lead to an easy to
use regression suite without limitations in complexity.

Best regards,
Tobias

Lars Asplund

unread,
Jul 7, 2015, 4:39:07 AM7/7/15
to
Den måndag 6 juli 2015 kl. 16:59:17 UTC+2 skrev Tobias Baumann:
> Hi Lars,
>
> > Seems like you have very good progress!
> >
>
> Yes, I'm a bit suprised that everything went so fast ;)
>
> > You say that you have a huge design to test. Does this means that test time is an issue for you? You might have seen the -p option that allow you to run test cases in parallel on several cores. There are also discussions with other VUnit users to do load balancing between slaves using Jenkins plugins.
>
> Yes test time is absolutly an issue, but this depends on my IPs. These
> are mainly for video algorithm and thereore I have to simulate a
> complete frame, which can't parallelize effectivly. But I can try to run
> the same IP using different regression setups in parallel. I have to
> find out if this is possible with my Modelsim license. If I remember
> correctly there can only run one Modelsim instance at the same

Running in parallel with different setups is a good idea. Once you have that you can ask yourself if all these tests need to run with the full frame size. You can also select to run a subset of the tests on every commit and then let the rest run over night.

As you might have seen we also support GHDL to avoid that licence problem. We've had good support from the GHDL to make this happen. The updated version is yet to be released as a binary so you need to build from source.

Best Regards,
Lars

tuta...@gmail.com

unread,
Apr 5, 2016, 12:57:22 AM4/5/16
to
Hi Tobias,
I'm newbie to the jenkins use, I want to automate my vhdl tests using both modelsim and VUnit. Have you a tutorial, advice or an example that allow me start the first steps.
Thanks and Regards
Khalid
0 new messages