The Rise of RISC-V on Display at Workshop

The Rise of RISC-V on Display at Workshop

How are companies and research teams approaching RISC-V implementation? Presentations at the recent RISC-V Workshop conference revealed some intriguing strategies.

Who is using RISC-V? Judging from this year’s RISC-V Workshop, it appears many more firms have decided to enter the fray—with more to come.

Nvidia gave a presentation about how its proprietary Falcon (Fast Logic CONtroller) core will be replaced by RISC-V cores. Falcon is a RISC CPU used in a number of Nvidia’s chips, such as the Jetson TX2. Unfortunately, Falcon has limitations, including a 32-bit address space and no thread protection. RISC-V addresses the limitations with a 64-bit address space as well as features like ECC/parity support, an extensible ISA, and better security. The implementation will use the RV64IM_Sdef ISA.

SiFive has been a leader in the RISC-V space. Its HiFive1 board holds an FE310 RISC-V processor, one of the only commercially available RISC-V chips available. Among the company’s presentations at the workshop was one about an External Debug Definition for RISC-V. The definition allows for the incorporation of more powerful debugging support without requiring proprietary support and toolchains. Arm has a similar modular approach for its debug and trace facilities. The basic set of features in version v0.13 include selecting Harts, Halt – Resume, abstract commands, access to the program buffer, single-step support, debugging across reset/power down, and triggers.

SiFive’s competition has become fiercer, too, with more companies delivering RISC-V-based designs. For example, Syntacore presented its SCRx family of RISC-V cores. It starts with the SCR1, a minimal system that uses fewer than 15k gates. The top-end SCR5 supports virtual memory, SMP, and Linux, and runs at 1 GHz using 28-nm technology.

1. Here’s an example of using an embedded FPGA with Achronix SpeedCore technology in a RISC-V-based SoC.

Andes Technology unveiled its AndesCore family. The 32-bit family includes platforms like the N705. The N705 has a feature called PowerBrake, which allows the CPU clock rate to be dynamically throttled. These are features found in most high-performance processors, but aren’t part of the RISC-V definition because RISC-V is simply an ISA definition. These features are implementation-specific and transparent to the ISA. The AndeStar family uses RISC-V as a base subset.

The AndesCore NX25 moves into the 64-bit space. It has a five-stage pipeline, dynamic branch prediction, and local memory and cache with parity/ECC protection. It also features PowerBrake support, as well as support for StackSafe stack integrity and CoDense compact code.

AndesCores are showing up in a number of projects. Wave Computing’s Dataflow Processing Unit (DPU) uses an AndexCore as a control processor. The DPU, which targets machine-learning applications, consists of thousands of processing elements (PE).

FPGAs continue to play a major part with RISC-V adoption. I’ve already written about Microsemi’s Mi-V environment designed to bring FPGA-based RISC-V to software developers. Achronix is also supporting RISC-V with its Speedster FPGA family, as well as the custom SpeedCore platform. Of course, a RISC-V SoC could also include an embedded FPGA using SpeedCore technology (Fig. 1). The example shows a SiFive U500-based architecture.

2. Dynamic binary translation of RISC-V code to run on a VLIW platform requires hardware support.

One interesting presentation was given by Rokicki Simon, Steven Derrien, and Erven Rohou from the Université de Rennes 1 and Inria Rennes entitled “RISC-V Hardware-Accelerated Dynamic Binary Translation.” It essentially takes RISC-V code and runs it on a VLIW platform using hardware support (Fig. 2).

RISC-V is still the new kid on the block, and lots of competition comes by way of Arm. It offers many advantages, and more in the industry have taken note and making use of them.

 

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish