File | Date | Author | Commit |
---|---|---|---|
dev | 2014-10-28 |
![]() |
[fd8768] Compilation warnings removed |
doc | 2013-03-12 |
![]() |
[135119] updated README.md |
.gitattributes | 2013-03-12 |
![]() |
[9b3b2b] added gitattributes |
.gitignore | 2013-03-12 |
![]() |
[5c5080] Adding QScintilla |
COPYING | 2013-12-17 |
![]() |
[8e2d6b] Update COPYING with correct license file |
CREDITS | 2013-03-12 |
![]() |
[135119] updated README.md |
LICENSE.APACHE2 | 2013-03-12 |
![]() |
[135119] updated README.md |
LICENSE.GPL3 | 2013-03-12 |
![]() |
[135119] updated README.md |
NOTICE | 2013-03-12 |
![]() |
[135119] updated README.md |
README.md | 2013-10-27 |
![]() |
[2c80ce] Update README.md |
The aim of the UVE project is to create software that automatically generates
a verification testbench (TB) written in [SystemVerilog (SV)]
(http://www.systemverilog.org/) and integrating the [UVM]
(http://www.uvmworld.org/) methodology.
UVE makes the rapid development of a verification environment a simple process.
The generated TB is directly able to perform random actions on the DUV (design
under verification). For this UVE provides a graphical user interface, a code
generator, compilation scripts and a library of verification IPs (VIP). One of
the main innovations of UVE is a list of TODOs in the TB code which help in
finalizing the TB. This is especially useful for developers not familiar with
SV and/or UVE, but also experienced developers profit from that easy to use
task list.
Moreover, the graphical interface lets the user observe the structure of the
generated testbench. Files can be accessed easily by double clicking on the
graphical view. Simulation can be launched directly from the tool.
For more information visit our homepage: www.systemverilog.ch
You can get the [latest UVE installer for windows form our homepage]
(http://www.systemverilog.ch/downloads/) our you can build the source yourself
with the instructions below.
This is the component used to build the code editing feature. It's already
present in the repository, but has to be installed
manually. This is done by opening the Qt Console. You should find it in your
START menu, it might be called something like Qt 5.3 for Desktop (MinGW 4.8 32 bit).
Inside the console you have to navigate to the folder
dev\qscintilla\qscintilla_uve\Qt4Qt5 in your repository.
If there exist the subfolders release and debug, delete them.
Then execute the following commands in this order in the command prompt:
>qmake qscintilla.pro
>make
>make install
or in the MinGW version
>qmake qscintilla.pro
>mingw32-make
>mingw32-make install
If an error like this "Makefile.Debug:60: *** missing separator. Stop."
appears, MinGW is not installed. On Qt Creator 2.4.1 or older
( check Help->About Qt Creator... ) you can check if you have MinGW installed
by going to Help->Start Updater in the Qt Creator Menu. Then select Package
Manager on the Maintain Qt SDK dialog that opens. Upon clicking Next you
get to the Select components screen where you should find
Miscellaneous-> MinGW x.x. Put a tick in the box and continue the installation
with Next. If you have a newer version of Qt Creator you can install minGW
with the [latest Windows installer from their website]
(http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/).
Install Bison with the installer from [their website]
(https://www.gnu.org/software/bison/) (recommended: v2.4.1) or Bison for Windows
(recommended: v2.4.1) in a folder without
spaces in it's name and location (recommended: C:\GnuWin32), else it will not
work. Then add the location of the bin folder in the installation directory to
the environment variable PATH (e.g. C:\GnuWin32\bin).
For flex download a zip file from their website and extract the files (without any folders) in zip file to the bin folder of Bison or install Flex for Windows to the same destination as Bison.
Open QtCreator and select Open Project.... Open the file /dev/gui/uve.pro.
Then on the Project Setup dialog you get the possibility to choose between
different Create Build Configurations. If you select None everything should
be fine. When you choose another option, you have to copy the
/dev/uveapp/templates folder to the parent folder of the generated executable,
otherwise the generation process won't work. Finally to be able to see the help
documentation, copy the folder \doc\UVEUserManualenglish into the parent
folder of the executable.