MicroTESK for RISC-V Installation Guide¶

Installation and User Guide¶

• Table of contents
• MicroTESK for RISC-V Installation Guide
• Installation and User Guide
  • Installation
    • System Requirements
    • Installation Steps
    • Setting Environment Variables
      • Windows
      • Linux and OS X
    • Installation Directory Structure
  • Using MicroTESK
    • Compiling ISA specifications
    • Generating and compiling test programs

Installation¶

System Requirements¶

MicroTESK is a set of Java-based utilities that are run from the command line. It can be used on Windows, Linux and OS X machines that have JDK 1.7 or later installed. To be able to recompile the RISC-V ISA specifications, Apache Ant version 1.8 or later is required.

Installation Steps¶

1. Download from https://forge.ispras.ru/projects/microtesk-riscv/files and unpack the MicroTESK installation package (the .tar.gz file, latest release) to your computer. The folder to which it was unpacked will be further referred to as the installation directory (<installation dir>).
2. Declare the MICROTESK_HOME environment variable and set its value to the path to the installation directory (see the Setting Environment Variables section).
3. Set the <installation dir>/bin as the working directory (add the path to the PATH environment variable) to be able to run MicroTESK utilities from any path.

Setting Environment Variables¶

Windows¶

1. Open the System Properties window.
2. Switch to the Advanced tab.
3. Click on Environment Variables.
4. Click New... under System Variables.
5. In the New System Variable dialog specify variable name as MICROTESK_HOME and variable value as <installation dir>.
6. Click OK on all open windows.
7. Reopen the command prompt window.

Linux and OS X¶

Add the command below to the ~.bash_profile file (Linux) or the ~/.profile file (OS X):

export MICROTESK_HOME=<installation dir>

To start editing the file, type vi ~/.bash_profile (or vi ~/.profile). Changes will be applied after restarting the command-line terminal or reboot. You can also execute the command in your command-line terminal to make temporary changes.

Installation Directory Structure¶

The MicroTESK installation directory contains the following subdirectories:

arch	Examples of microprocessor specifications and test templates for the described designs
bin	Scripts to run features of MicroTESK (modelling and test generation)
doc	Documentation on MicroTESK
etc	MicroTESK configuration files
gen	Generated Java models of the specified microprocessor designs
lib	JAR files and Ruby scripts to perform modelling and test generation tasks
src	Source code of MicroTESK

Using MicroTESK¶

Compiling ISA specifications¶

NOTE: Compiling ISA specifications is required only if the user is going to modify them. The distribution package already contains compiled specifications. By default, the ISA specifications are compiled for revision RV64{I,M,F,D,C}.

The description of the RISC-V ISA is provided in formal specifications in the nML language. They can be found in the <installation dir>/arch/riscv/model folder. They need to be compiled to be used by MicroTESK.
To compile them, a user needs to run the Make file stored in the <installation dir>/arch/riscv/model folder:

cd $MICROTESK_HOME/arch/riscv/model
make

Generating and compiling test programs¶

Test programs are generated on the basis of test templates. Examples of test templates are provided in the the <installation dir>/arch/riscv/templates folder. Most of them contain comments describing their purpose.

To run generation of a test program, a used need to run a Make file located in the same folder. For example:

cd $MICROTESK_HOME/arch/riscv/templates/torture
make torture

The Make script generates a test program and compiles it with the GNU toolchain. The generated and compiled test program is placed into the <installation dir>/output/torture/torture folder.
To successfully compile the test program, the following tools are required to be installed in the machine: riscv64-unknown-elf-gcc and riscv64-unknown-elf-objdump.

The debug output of the generator is printed into the torture.stderr and torture.stdout files. These files need to be investigated if any problems occur during test program generation.