RISC-V 32-Bit Topics and Tutorial

This appendix describes topics relevant to GNAT for bareboard 32-bit RISC-V and also presents a tutorial on building, running, and debugging an Ada application on an embedded 32-bit RISC-V board.

Supported Processors and Run-Time Libraries

GNAT for bareboard 32-bit RISC-V supports processors conforming to the RISC V 32-bit instruction set.

Run-time support is provided for HiFive1 developer board from SiFive. The following run-time library is pre-built:

  • zfp-hifive1

All pre-built run-time libraries include the necessary low-level hardware startup and initialization functionality required to run applications on the developer board. In many cases, the pre-built run-time libraries will run on other developer boards and processors if they share a similar configuration to these pre-built run-times. If your processor or board uses a different configuration, you can modify and rebuild the pre-built run-time to meet your needs, or if you wish to target a different processor within the supported families, you can retarget the run-time. The run-time libraries are largely independent of the underlying hardware, simplifying this process.

Getting Started

Developing with GNAT for bareboard 32-bit RISC-V is similar to native GNAT development, with two important differences. First, when building for a bareboard target you need to specify both the target processor and the run-time library. This can be defined in a project file (either directly or via the project properties dialog in GNAT Studio) or on the command line. For details on how to specify the target and run-time library for your project, see Introduction to GNAT for Cross Platforms. For all supported 32-bit RISC-V boards, the target ‘riscv32-elf’ needs to be specified.

For example, the following project file fragment shows both the target and the run-time library specified via their respective attributes. In this example, a 32-bit RISC-V target and the ‘Zero Foot Print’ HiFive1 run-time library is specified:

project Demo is
   for Runtime ("Ada") use "zfp-hifive1";
   for Target use "riscv32-elf";
end Demo;

The second difference is how programs are run and debugged. This is dependent on your setup and the tools you use. In many cases, GNAT Studio can be used to debug your program. See Debugging for details.

Getting Started with GNATemulator

This guide describes how to set up, build, run, and debug an Ada application using GNATemulator with the zfp-hifive1 run-time. Setup for both Windows and Linux hosts is covered. While this section focuses on GNATemulator, most of the steps contained within this section are independent of the application and the target hardware itself.

To begin this setup, it is assumed that GNAT for bareboard 32-bit RISC-V has been installed and that the install bin directory is in the PATH environment variable.

Once installed, ensure that the installation bin directory (by default bin/usr/local/bin) included in your PATH.

Creating a new Project

Launch GNAT Studio:

$ gnatstudio

If this is your first time running GNAT Studio, note that GNAT Studio will create a configuration directory and will alert you via a pop-up dialog box. Press ‘OK’ to close that box and continue. A ‘Tip of the Day’ dialog will appear. Press Close to dismiss it.

When on the Welcome page, click on Create new project and select Simple Ada project, and then click on Next. Change Location and Settings appropriately and press Apply.

The project view is now displayed; it is then possible to edit project properties by right-clicking on the project name in the Project tab, and selecting Project->Properties.

The project properties are now displayed. Open the Toolchains tab, and make sure that the riscv32-elf toolchain is selected and that the Ada run-time is zfp-hifive1. Then click on Save.

You can now navigate the project tree and add your source code.


Within GNAT Studio, build the project using either the Build Main button on the toolbar, or the Build/Project->Build All menu entry. In the latter case, if a pop-up window appears, press the Execute button in order to build with the default settings.

As GNAT Studio builds the project, it will display the Messages view at the bottom of the GNAT Studio window to show information about the build. On a successful build, the Memory Usage view will graphically display the memory usage of the program, unless the preference is disabled. (See the preference Build Targets/Project/Build Main page, among others, containing the Display memory usage check-box.)

Running the Program

Within GNAT Studio, run your program on the emulator using the Run with Emulator toolbar button or the Build/Emulator->Run with Emulator menu entry.

As the program executes, it will display its output, if any, in the riscv32-elf-gnatemu view.

Debugging the Program

In GNAT Studio, click on the Debug with Emulator button on the toolbar. This will start a GNAT Studio debug session and launch the necessary tools required to debug the program on the board from GNAT Studio. The emulator will be automatically launched. Debugging a program on the emulator through GNAT Studio is similar to debugging a native program:

  • The program can continue to the next breakpoint by pressing the Continue button on the toolbar or by using the Debug/Continue menu item.
  • The program can be stepped through statements using the corresponding menu items in Debug menu and buttons on the toolbar.
  • The program can be interrupted by pressing <ctrl>-\, or through the Debug/Interrupt menu.
  • Breakpoints can be set via the Breakpoints view, by clicking on the line numbers in the source editor while the program is interrupted or by right-clicking on the desired line and selecting Set breakpoint on line ... from the Debug menu.
  • Variables can be queried from the Variables view or by hovering the mouse over a variable with the program interrupted.

GNAT Studio also provides a Debugger Console view that allows shell access to the underlying GDB client that is debugging the program. The GDB commands that correspond to the above debugging tasks can be entered directly into the console if desired.

The debugging session can be exited via the Debug/Terminate menu or by issuing the quit command in the Debugger Console.