Debugging the RV32M1-VEGA RISC-V with Eclipse and MCUXpresso IDE

The Arm Cortex cores are everywhere. I like (and use) them a lot. Don’t take me wrong: maybe Arm needs some competition? It is very refreshing to see that something new is getting a lot of attention: RISC-V!

RISC-V is an open instruction set architecture, and so far SiFive was *the* vendor offering real chips. I’m already using a RISC-V from SiFive (see Open Source RISC — Eclipse with RISC-V on the SiFive HiFive1 Board).

However, a new RISC-V player emerged: OpenISA. On that site, there was an offer for a free board for which I applied. I nearly have forgotten about this, but after several weeks afterwards I received two boards. The website and discussions in the communities indicated it, and the logo on the device confirmed it: it is Freescale (well, now NXP) which produced that device. What they have done is create a community page on open-isa.org and this where the board ‘getting started’ points to, and what I have used to set up my environment. It seems that NXP has started a kind of test run ‘under the radar,’ which is interesting on its own.

Compared to the SiFive board, I’m happy to report that the VEGA RV32M1 can be debugged properly with a 10-pin SWD/JTAG connector.

The board is very similar to other ‘FRDM’ (or Freedom) boards from Freescale/NXP. It features an NXP Kinetis K26 as UART (and possibly debug? I did not find a firmware) bridge.

So I used a SEGGER J-Link Mini to debug the board.

There are four cores (plus the Kinetis K26) on the board. Which core to boot is selectable, but I have not explored that yet.

Because each half (RI5CY/M4F and Zero-RISCY/M0+) share the same bus, it is more like a dual-heterogeneous core setup. Interestingly, the two RISC-V cores are from the PULP project at the ETH Zurich.

The ‘getting started’ guide provides videos and basic steps to set up an environment, explaining it for using make files or with a DIY Eclipse IDE. I decided to use the NXP MCUXpresso IDE instead, and that worked very well. I used the MCUXpresso IDE V10.3.1 in this article, and it needs only the GNU MCU Eclipse plugins and a toolchain to develop for RISC-V.

• I assume that the MCUXpresso IDE is already installed, otherwise it is available from http://www.nxp.com/mcuxpresso/ide.

• Go to https://github.com/open-isa-org/open-isa.org/releases and download the toolchain and SDK (marked below for Windows). The Arm SDK is optional and only needed to develop for the Arm cores.

• Run the installer for the RISC-V SDK and install it into c:\vega (which is the default).

• Install RISC-V SDK.

• Optionally: Install the Arm SDK into the same folder as above.

• Create a folder ‘Toolchain’ in C:\Vega and extract the two zip files from the Toolchain zip/archive into it.

• Toolchain zip files.

• Extract the content of openocd.zip into a folder named openocd.

• Extract the content of the riscv32-unknown-elf-gcc.zip into a folder named riscv32-unknown-elf-gcc

• The installation structure should now look like this:

• Windows Build tools (Make, rm): If not already installed, go to https://gnu-mcu-eclipse.github.io/windows-build-tools/install/ and download the archive from https://github.com/gnu-mcu-eclipse/windows-build-tools/releases, extract it into the Toolchain folder:

• In MCUXpresso IDE, use the following URL as update site in Eclipse (Help > Install New software): http://gnu-mcu-eclipse.netlify.com/v4-neon-updates and install the plugin(s):

With this, all the plugins and tools are installed.

I’m using a J-Link EDU Mini. There are three SWD/JTAG headers on the board: use the one near the RV32M1 microcontroller.

The toolchain comes with a pre-built OpenOCD package which works with a SEGGER J-Link (see https://wiki.segger.com/OpenOCD). To use it, launch the UsbDriverTool:

Then install WinUSB on the J-Link driver. For this, the J-Link has to be plugged into the host:

NOTE: By doing this, I cannot use the J-Link probes with the SEGGER J-Link software anymore. To use the J-Link again the ‘normal’ way, I have to restore the default driver again:

In the MCUXpresso IDE, verify that the toolchain settings in the workspace settings (menu Window > Preferences):

Global Build Tools Path:

C:\Vega\GNU MCU Eclipse\Build Tools\2.11-20180428-1604\bin

RISC-V Toolchain:

C:\Vega\Toolchain\riscv32-unknown-elf-gcc\bin

OpenOCD:

C:\Vega\Toolchain\openocd\bin

Import a project from the SDK, e.g:

C:\Vega\rv32m1_sdk_riscv\boards\rv32m1_vega\demo_apps\bubble\ri5cy\riscveclipse

Drag and drop the .project file into the IDE. Because the projects in the SDK are using project relative links, I have to ‘link’ to it:

With the toolchain setup correctly, this should build fine:

The projects include launch configurations for OpenOCD (Menu Run > Debug Configurations). Verify that the correct openOCD binary is used with its configuration file:

Power the board with the J8 USB connector:

With this, hit ‘Debug’ and I am debugging.

Using a RISC-V core, or as in this case using multiple ones is fun, and I’m glad to see that software and tools are evolving. RISC-V could be the next big thing, but for sure it might take a while to be widely available. According to this EE Journal article, more boards might be available in the future.

What’s next? There is a new FreeRTOS release available for RISC-V, so I’m going to try that one…

Happy RISCing!

Originally published at mcuoneclipse.com on March 4, 2019.