CORE-V MCU DevKit

Product Description

The CORE-V MCU DevKit is a turnkey, open-source development and prototyping platform for the CORE-V MCU System on Chip. The CORE-V MCU DevKit enables makers of IoT and embedded systems to evaluate the performance of the CORE-V MCU, to interconnect with WiFi and the IoT cloud, and to develop and test software using the CORE-V SDK.

Estimated Shipping Date: June 19, 2024

The CORE-V MCU DevKit includes these features:

• CORE-V MCU
• CV32E40P processor core
• Quicklogic ArticPro 2 eFPGA
• 4 MB flash memory
• Ashling Opella-LD onboard JTAG debug module
• USB-C for terminal and onboard debug access
• JTAG connector for external debug access
• Espressif AWS IoT ExpressLink Module for AWS IoT cloud interconnect
• mikroBUS onboard socket, allowing access to a vast range of mikroBUS modules
• Himax HM01B0 Ultralow Power CMOS Image Sensor
• I2C temperature sensor
• Several LEDs
• Reset button and general purpose button
• Dimensions 75 mm x 100 mm
• Power supply via USB-C or barrel connector (5V - 18V in)

CORE-V MCU SDK

The CORE-V MCU DevKit is supported by OpenHW Group’s open-source CORE-V MCU SDK. The SDK comprises the following features

• Eclipse based IDE
• Debug support
• FreeRTOS
• CORE-V GNU GCC tool chain
• Peripheral driver libraries
• Example Code

The CORE-V MCU SDK Quickstart Guide includes links and instructions to download and bring up the SDK on Linux and Windows.

About the Team

OpenHW Group is a not-for-profit, global organization registered in Canada and driven by its members and individual contributors where HW and SW designers collaborate in the development of open-source cores, related IP, tools and SW such as the CORE-V Family of open-source RISC-V cores.

This campaign is a special collaboration with OpenHW Group and GroupGets. We're excited about being the newest member of the group to help bring about more new products powered by CORE-V, created by OpenHW Group. We coordinated with the OpenHW team to manage the manufacturing and test of sample units designed by Amazon.

Watch the Embedded World CORE-V MCU DevKit Launch

Product Specifications

CORE-V MCU DevKit Architecture 

The architecture of the DevKit is shown below:

Let’s review the main features of the DevKit, starting with the CORE-V MCU.

CORE-V MCU

At the heart of the DevKit is the CORE-V MCU, an ASIC developed by the OpenHW community and fabricated in Global Foundry’s 22FDX process. The CORE-V MCU provides an evaluation and development platform for OpenHW’s fully-verified CV32E40PV1.0 embedded-class processor core. The CORE-V-MCU integrates the processor core with a set of on-chip peripherals, memory, and Quicklogic’s embedded FPGA (eFPGA) technology.  The CORE-V MCU logic, with the exception of the eFPGA, is available on Github in open-source RTL under the permissive Solderpad 2.1 license.

CV32E40P Processor Core

The CV32E40P processor core is the first core released by OpenHW Group on Github in open-source RTL. It is a 4-stage, in-order 32-bit RISC-V processor core. The CV32E40P, developed through the collaborative efforts of the OpenHW community, is completely open-source and released under the permissive Solderpad 2.1 license. The ISA of CV32E40P as instantiated within the CORE-V-MCU supports the following instructions:

A block diagram of the CV32E40P core is shown below.

On-Chip Memory

The CORE-V MCU includes 512K-byte of on-chip SRAM. The memory is organized as two 32K-byte banks of non-interleaved SRAM, typically used for program store, plus four 112K-byte banks of interleaved SRAM, typically used for data store. The interleaved memory architecture provides high speed access to memories for both the processor core and I/O peripherals.

On-Chip Peripherals

The CORE-V MCU includes the following peripherals:

• 2 UARTs
• 2 QSPI masters
• 2 I2C masters
• 1 SDIO
• 1 CI (Camera)
• 1 GPIO unit with 32 I/O
• 1 I2C slave
• 1 Advanced Timer (PWM) with 4 channels
• JTAG

Embedded FPGA

The embedded FPGA (eFPGA) subsystem integrated within the CORE-V MCU is based on Quicklogic’s ArcticPro 2 architecture. This is a silicon-verified, production-proven eFPGA for MCU/SoC/custom ASIC applications. The eFPGA IP enables the flexibility to easily program custom functions, hardware accelerators and security algorithms after an SoC has been manufactured. Programming the eFPGA within CORE-V MCU will be supported by Open Source tools to create the bitstream. Example designs will be provided.

CORE-V MCU DevKit Expresslink Module

The CORE-V MCU DevKit includes Espressif’s AWS IoT ExpressLink module, which provides WiFi and out-of-the-box, seamless connectivity to the AWS IoT ExpressLink cloud service. This allows DevKit-based IoT applications, such as the OpenHW-developed temperature sensing demonstration to interconnect with AWS IoT cloud services.  

CORE-V MCU DevKit MikroBus Header

The CORE-V MCU DevKit includes a mikroBUS™ socket, comprising a pair of 1×8 female headers that support interconnection to a wide range of display, sensor, actuator and other modules.

CORE-V MCU DevKit Debug Interface

The CORE-V MCU DevKit supports on-chip debugging of the CORE-V MCU via a JTAG interface and board connector. Additionally, the debug signals are converted to USB via the Ashling Opella-LD debug probe and brought out on USB-C.

CORE-V MCU DevKit Flash Memory

The CORE-V MCU DevKit provides a 4 MB flash memory used to store program code and other data. In the case of program code, a CORE-V MCU ROM-based bootloader loads the flash memory into the CORE-V MCU internal 512 KB SRAM.

CORE-V MCU DevKit Camera

The CORE-V MCU DevKit supports a Himax camera (Ultra Low Power CMOS Image Sensor) connected to the CORE-V MCU via Camera Serial Interface. The camera is mounted on a flex cable that allows the user to orient the camera in a variety of directions. 

CORE-V MCU DevKit Power Supply

The CORE-V MCU DevKit includes a switching power supply which can accept 5V from the USB-C, or 5V - 18 V from the 2.1 mm barrel connector. 

Unit Deliverable

One CORE-V MCU Devkit

Unit Price

$199.00

Availability

Campaign Unsuccessful, ends when minimum unit count reached

Lead Time

14 Days after campaign end date