README : Kactus2 Copyright (c) 2012-2018 Tampere University of Technology http://funbase.cs.tut.fi
Kactus2 is a toolset for designing embedded products, especially FPGA-based MP-SoCs. The aim is easier IP reusability and integration for both hardware and software. The tool is based on IEEE 1685-2014 "IP-XACT" standard.
Windows installer and tar-package for Linux are available in SourceForge
What you can do with Kactus2
Package IPs for reuse and exchange
- Import your existing IPs as IP-XACT components
- Create new IP-XACT components and generate their HDL module headers
- Reuse IP-XACT files from any standard compatible vendor
- Reuse the IPs in your designs and connect them with wires and busses
Create HW designs with hierarchy
- Create multilevel hierarchies, where a design has multiple sub-designs
- Configure component instances in designs, including the sub-designs
- Use generator plugins to create HDL with wiring and parameterization
Integrate HW and SW
- Use memory designer to preview memory maps and address spaces in your hierarchy
- Package software to IP-XACT components and map them to hardware
- Generate makefiles that build executables with rules defined in IP-XACT components
What you cannot do with Kactus2
- Behavioral logic: Neither Kactus2 nor IP-XACT handles module implementations
- Synthesis or simulation: These require tools that are specificly created for the purpose
Examples and tutorials
Example IPs are available in GitHub here.
Video tutorials are available in Youtube.
An installer (link above) will guide you through the installation on Windows platforms.
If you want to build Kactus2 on Windows, see separate instructions in our project management site: https://kactus2.cs.tut.fi
Linux build and run
1. Install Qt5
To build and run Kactus2, Qt5 must be installed on your system. If you already have Qt installed, you can skip to step 2. Otherwise, select installing Qt with either using a package manager (option a) or manually (option b):
a) Install Qt5 packages using a package manager (requires admin privileges). The following packages are required (on Ubuntu):
sudo apt-get install qt5-default qttools5-private-dev qttools5-dev-tools libqt5svg5-dev
b) Manually download and install from https://www.qt.io/download/
When using manually installed Qt5, you need to make sure that Kactus2 install is configured accordingly: Open file configure in the Kactus2 root directory and set the path to Qt5 binaries in the variable QTBIN_PATH.
Please do note the slash at the end of the path.
2. Build the sources
First, get the Kactus2 source files. We recommend using the release tar-package (link above) which has all Windows-specific files removed. Extract the files and navigate to the Kactus2 root directory.
mkdir ~/kactus2 tar -xvf kactus2-3.4.0.tar.gz -C ~/kactus2 cd ~/kactus2
Select installation either for all users (option a) or customized target (option b) below:
a) Default installation for all users (requires admin privileges).
Open file .qmake.conf and check that the paths are compatible with your Linux distribution. The defaults should work with Ubuntu 64-bit, Debian and CentOS 7 64-bit, but on some systems you may have to change lib_path from /usr/lib to /usr/lib64.
Now run following commands:
./configure make sudo make install
After the installation, skip to section 3.
b) Customized installation target. This option can be used for a local installation for the current user (e.g. in ~/kactus2) as well as shared installation in a specific directory (e.g. /opt/edatools/kactus2).
Open file .qmake.conf and set the installation directory in variable LOCAL_INSTALL_DIR.
By default, the shared libraries are installed in the same directory, but can be configured by setting the lib_path on line 44.
Now run the following commands:
./configure make make install
sudo make install, if the current user has no write permissions to the target directory
Finally, make sure the shared libraries can be found by the program loader. If the installation
is shared between multiple users, consider listing the libraries in /etc/ld.so.conf. For example,
create the file /etc/ld.so.conf.d/kactus2-3.4.0.conf and in it add a single line that contains the
path to the installation directory (e.g. /opt/edatools/kactus2). Run
ldconfig to update the paths
in the loader.
Please note, if you do ./configure with wrong Qt binaries, you will have to delete the generated
makefiles before configuring again. The easiest way to do this, is to run command
3a. Run Kactus2 GUI
There are three ways to run Kactus2 depending on your system and installation setup.
a) A default installation shared between users. Run:
b) A local installation from the installation directory. Run:
If the library paths are set in /etc/ld.so.conf, the binary can be run directly. Example:
c) In some systems, a link to the executable is created, if Kactus2 was installed for all users. Run:
Please note a recent change to lower-case binary name i.e. kactus2, not Kactus2.
3b. Run Kactus2 command-line (experimental)
Some tasks may be run in the command-line without the GUI. Currently only Verilog and VHDL
generators supports this feature and can be executed with command
generate_vhdl. Additional options are required as detailed below.
kactus2 generate_verilog -c tut.fi:cpu.logic:alu:1.0 -w structural_verilog -o ./rtl_out
This will generate structural Verilog for the
its sub-component hierarchy defined in
Kactus2 supports the following general command-line options:
-h, --help: Show the application usage help and exit.
-v, --version: Show the application version and exit.
Please note that the command-line interface is an experimental feature and very likely subject to changes in the near future.
Settings and configurations
Kactus2 uses a settings file storing user-specific tool settings. The default location is ~/.config/TUT/Kactus2.ini in Linux and C:\Users<username>\AppData\Roaming\TUT\Kactus2.ini in Windows. The location can be checked on the general settings page in Kactus2.
A system wide default settings file is located in /etc/xdg and C:\ProgramData, respectively. This will be used as a base for any new user-specific settings and a fallback mechanism, if the user's file is missing a requested value.
Modifying the settings files manually is not recommended and should be done only by advanced users. Most of the time all required changes can be applied in the Kactus2 GUI.
In addtion, Kactus2 uses the file configure.cfg for updating the users' settings when new setting options are introduced in the tool. Please do not modify this file as it will break the compatibility with earlier versions.
Community Guidelines & Contributions
Please see CONTRIBUTING.md for details.
Antti Kamppi, Joni-Matti Määttä, Lauri Matilainen, Timo D. Hämäläinen, Mikko Teuho, Juho Järvinen, Esko Pekkarinen, Janne Virtanen
Kactus2 is linked with Qt 5.10.1, copyright Digia Plc. (LGPL).
Kactus2 uses Icons8 provided by Icons8 LLC
This software is licenced under the GPL2 General Public License.
Kactus2 is also available for dual licencing. Please contact email@example.com to purchase a commercial licence.