RA4E2 Evaluation Kit

Overview

The RA4E2 Group delivers up to 100 MHz of CPU performance using an Arm® Cortex®-M33 core with 128 KB of code flash memory, 4 KB of data flash memory, and 40 KB of SRAM. RA4E2 MCUs offer high-performance and optimized peripheral functions along with the smallest package options, including space-saving 36-pin BGA and 32-pin QFN packages. The RA4E2 Group offers a wide set of peripherals, including USB Full Speed, CANFD, I3C, and ADC.

The MCU in this series incorporates a high-performance Arm Cortex®-M33 core running up to 100 MHz with the following features:

MCU Native Pin Access

  • R7FA4E2B93CFM MCU (referred to as RA MCU)

  • 100 MHz, Arm® Cortex®-M33 core

  • 128 kB Code Flash, 40 kB SRAM

  • 64 pins, LQFP package

  • Native pin access through 2 x 14-pin and 1 x 40-pin male headers

  • MCU current measurement points for precision current consumption measurement

  • Multiple clock sources - RA MCU oscillator and sub-clock oscillator crystals, providing precision 20.000 MHz and 32,768 Hz reference clock. Additional low-precision clocks are available internal to the RA MCU

System Control and Ecosystem Access

  • USB Full Speed Device (micro-AB connector)

  • Three 5 V input sources

    • USB (Debug, Full Speed)

    • External power supply (using surface mount clamp test points and J31 through holes)

  • Three Debug modes

    • Debug on-board (SWD)

    • Debug in (SWD)

    • Debug out (JTAG, SWD)

  • User LEDs and buttons

    • Three User LEDs (red, blue, green)

    • Power LED (white) indicating availability of regulated power

    • Debug LED (yellow) indicating the debug connection

    • Two User buttons

    • One Reset button

  • Five most popular ecosystems expansions

    • 2 Seeed Grove® system (I3C/Analog) connectors

    • SparkFun® Qwiic® connector

    • 2 Digilent PmodTM (SPI and UART) connectors

    • ArduinoTM (Uno R3) connector

    • MikroElektronikaTM mikroBUS connector

  • MCU boot configuration jumper

Special Feature Access

  • CAN FD (3-pin header)

Hardware

Detailed hardware features for the RA4E2 MCU group can be found at RA4E2 Group User’s Manual Hardware

RA4E2 MCU group feature

RA4E2 Block diagram (Credit: Renesas Electronics Corporation)

Detailed hardware features for the EK-RA4E2 MCU can be found at EK-RA4E2 - User’s Manual

Supported Features

The ek_ra4e2 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

ek_ra4e2/r7fa4e2b93cfm target

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-M33 CPU1

arm,cortex-m33

ADC

on-chip

Renesas RA ADC node1

renesas,ra-adc

CAN

on-chip

Renesas RA CANFD controller global1

renesas,ra-canfd-global

on-chip

Renesas RA CANFD controller1

renesas,ra-canfd

Clock control

on-chip

Renesas RA Clock Generation Circuit external clock configuration1

renesas,ra-cgc-external-clock

on-chip

Generic fixed-rate clock provider3

fixed-clock

on-chip

Renesas RA Sub-Clock1

renesas,ra-cgc-subclk

on-chip

Renesas RA Clock Generation Circuit PLL Clock1

renesas,ra-cgc-pll

on-chip

Renesas RA Clock Control node pclk block1

renesas,ra-cgc-pclk-block

on-chip

Renesas RA Clock Control Peripheral Clock7 4

renesas,ra-cgc-pclk

DAC

on-chip

Renesas RA DAC Controller Global1

renesas,ra-dac-global

on-chip

Renesas RA DAC Controller1

renesas,ra-dac

Flash controller

on-chip

Renesas RA family flash high-performance controller1

renesas,ra-flash-hp-controller

GPIO & Headers

on-chip

Renesas RA GPIO I/O Port5 2

renesas,ra-gpio-ioport

Input

on-board

Group of GPIO-bound input keys1

gpio-keys

Interrupt controller

on-chip

ARMv8-M NVIC (Nested Vectored Interrupt Controller)1

arm,v8m-nvic

LED

on-board

Group of GPIO-controlled LEDs1

gpio-leds

Miscellaneous

on-chip

Renesas RA SCI controller1 1

renesas,ra-sci

on-chip

Renesas RA External Interrupt2 14

renesas,ra-external-interrupt

MMU / MPU

on-chip

ARMv8-M MPU (Memory Protection Unit)1

arm,armv8m-mpu

MTD

on-chip

Flash memory binding of Renesas RA family2

renesas,ra-nv-flash

on-board

Fixed partitions of a flash (or other non-volatile storage) memory1

fixed-partitions

PHY

on-board

Simple GPIO controlled CAN transceiver1

can-transceiver-gpio

Pin control

on-chip

The Renesas RA pin controller is a node responsible for controlling pin function selection and pin properties, such as routing a SCI0 RXD to P6101

renesas,ra-pinctrl-pfs

PWM

on-chip

Renesas RA Pulse Width Modulation1 3

renesas,ra-pwm

RNG

on-chip

Renesas RA TRNG1

renesas,ra-trng

Serial controller

on-chip

Renesas RA SCI UART controller1 1

renesas,ra-sci-uart

SPI

on-chip

Renesas RA SPI controller1 1

renesas,ra-spi

SRAM

on-chip

Generic on-chip SRAM description1

mmio-sram

Timer

on-chip

ARMv8-M System Tick1

arm,armv8m-systick

Watchdog

on-chip

Renesas RA Watchdog (wdt)1

renesas,ra-wdt

Programming and Debugging

Applications for the ek_ra4e2 board target configuration can be built, flashed, and debugged in the usual way. See Building an Application and Run an Application for more details on building and running.

Flashing

Program can be flashed to EK-RA4E2 via the on-board SEGGER J-Link debugger. SEGGER J-link’s drivers are available at https://www.segger.com/downloads/jlink/

To flash the program to board

  1. Connect to J-Link OB via USB port to host PC

  2. Make sure J-Link OB jumper is in default configuration as describe in EK-RA4E2 - User’s Manual

  3. Execute west command

    west flash -r jlink
    

Debugging

You can use Segger Ozone (Segger Ozone Download) for a visual debug interface

Once downloaded and installed, open Segger Ozone and configure the debug project like so:

  • Target Device: R7FA4E2B9

  • Target Interface: SWD

  • Target Interface Speed: 4 MHz

  • Host Interface: USB

  • Program File: <path/to/your/build/zephyr.elf>

Note: It’s verified that we can debug OK on Segger Ozone v3.30d so please use this or later version of Segger Ozone

References