Overview
Description
The Renesas RA4M3 group of 32-bit microcontrollers (MCUs) uses the high-performance Arm® Cortex®-M33 core with TrustZone®. In concert with the secure crypto engine, it offers secure element functionality. The RA4M3 is built on a highly efficient 40nm process and is supported by an open and flexible ecosystem concept—the Flexible Software Package (FSP), built on FreeRTOS—and is expandable to use other RTOSes and middleware. The RA4M3 is suitable for IoT applications requiring vast communication options, future proof security, large embedded RAM, and low active power consumption down to 119µA/MHz running the CoreMark® algorithm from Flash.
Features
- 100MHz Arm Cortex-M33 with TrustZone
- Secure element functionality
- 512kB - 1MB Flash memory and 64kB SRAM with parity and 64kB SRAM with ECC
- 8kB Data Flash to store data as in EEPROM
- 1kB Stand-by SRAM
- Scalable from 64-pin to 144-pin packages
- Capacitive touch sensing unit (CTSU)
- USB 2.0 Full Speed
- CAN 2.0B
- Quad SPI
- SCI (UART, Simple SPI, Simple I2C)
- SPI/I2C multi-master interface
- SDHI and MMC
Comparison
Applications
Design & Development
Software & Tools
Sample Code
Boards & Kits
Models
ECAD Models
Schematic symbols, PCB footprints, and 3D CAD models from SamacSys can be found by clicking on the CAD Model links in the Product Options table. If a symbol or model isn't available, it can be requested directly from SamacSys.
Support
Support Communities
Renesas Academy
Support Communities
-
Is there any kind of chip reset cause function for the RA4M3?
Is there a register or function setup in the FSP that tells you the reset reason for the MCU (soft reset, hard reset, watchdog, etc.)?
Feb 17, 2022 -
RA4M3 bootloader guide
When I tried to use bootloader according to the document on ek-ra4m3 development board, I found that the final result was not achieved. According to the document, the bootloader program was created first, then the application program was created, then the application program was set, and finally xxx bin ...
Jun 8, 2022 -
RA4M3 Could not determine GDB version
Hello all, I've been having an issue lunching a debug session in e2 studio. The failure happens on determining the GDB version. I tried many things like providing the direct path to the gdb executable with no success, even though the same command works just fine in the command ...
May 1, 2025
FAQs
-
Linker Error in TrustZone non-secure projects for RA4M3 or RA4M2 with IAR Compiler
Last Updated:02/16/2021 This issue applies to FSP 2.2.0 and 2.3.0. When building RA4M3 or RA4M2 TrustZone non-secure projects, the following linker error is output: Error[Lc009]: "OSPI_DEVICE_0_START" undefined Error[Lc009]: "OSPI_DEVICE_1_START" undefined To work ...
Feb 16, 2021 -
RA4M2, RA4M3, RA6M4, RA6M5: Is it possible to change the Trustzone boundaries via OTA?
... change the IDAU settings in firmware and it is not possible to be manipulated during remote update (e.g. OTA). So the answer is no, the Trustzone boundaries cannot be changed during OTA. Resources: Securing Data at Rest Using the Arm® TrustZone® Suitable Products RA4M2,RA4M3,RA6M4,RA6M5
Oct 30, 2024 -
Correcting RAM Length for RA4M3 MCUs in FSP
The RAM length is incorrectly specified in the linker script for RA4M3 MCUs in FSP v2.2.0 through FSP 3.0.0. It is corrected in FSP 3.1.0. In versions before FSP 3.1.0 edit the memory_regions.ld file (or it's equivalent in other ...
Jul 6, 2021
Videos & Training
Introduction to the RA4M3 MCU group with industry-leading performance, security and memory enhancements for low power IoT applications.
Additional Videos
Events & Webinars
News & Blog Posts
Blog Post
Jan 28, 2022
|