Skip to content

Releases: renesas/rx-fsp

Release list

v1.0.0

v1.0.0 Latest
Latest

Choose a tag to compare

View all tags
@renesas-rx-fsp-development renesas-rx-fsp-development released this 25 Sep 12:45
v1.0.0
5001e2d

Release Notes

Flexible Software Package (FSP) for Renesas RX MCU Series, version 1.0.0.

Download the FSP with e2 studio Installer for this release, setup_rxfsp_v1_0_0_e2s_v2026-07.exe, from here.

If using IAR Embedded Workbench for RX, download the RX Smart Configurator for this release, setup_rxfsp_v1_0_0_sc_v2026-07.exe, from here.

All installers are available in the Assets section of this release.

Refer to the README.md in the FSP root folder for setup instructions, hardware details, and related links.

Tools (minimum version required)

New Features

  • Added support for the RX74M and RX74N MCU groups.
    • Includes support for the EK-RX74M, EK-RX74N, MCK-RX74M, and MCK-RX74N boards.
    • Key features:
      • Comprehensive set of drivers, middleware, industrial networking, motor control, security, storage, and RTOS components.
      • Industrial networking support including EtherCAT, lwIP TCP/IP, gPTP, and Ethernet connectivity.
      • Motor control middleware support including vector, current, speed, and position control.
      • Security support including Protect Zone, MCUboot, secure key injection, and PSA Crypto.
      • FreeRTOS support including kernel integration and middleware ecosystem support for embedded applications.
      • Azure RTOS support including ThreadX, NetX Duo, NetX Duo Crypto, and USBX.
      • Little/Big-endian and SBOM support for platform compatibility and software transparency.
    • Refer to the SUPPORTED_SOFTWARE.md for the complete list of supported modules and features.

Planned Support

  • J-Link will be supported in e2 studio 2026-10 version.
  • Visual Studio Code extension support for RX FSP projects will be available in 2026-10.
  • IAR Embedded Workbench support for RX74M/N will be available in 2026-10.

Unsupported Configurations or Features

  • CC-RX C++ projects are not supported.
  • Big-endian is not supported for Azure RTOS, FreeRTOS+FAT, rm_block_media_usb and ProtectZone.
  • Ethernet:
    • r_layer3_switch doesn't support C++.
  • MCUboot:
    • When MCUboot is configured with MbedTLS as the crypto stack, the following signature types are not supported: ECDSA-P384, RSA3072, ML-DSA44, and ML-DSA65.
    • MCUboot does not support operation when MCUboot Custom Crypto is selected as the crypto stack.
    • MCUboot does not support the booting images from external flash memory, Measured Boot, Data Sharing, or Boot Record.
    • MCUboot does not support multiple images.
    • MCUboot is not supported in IAR projects.
  • NetX Duo:
    • rm_netxduo_ether is not supported in IAR projects.
    • Multiple NetX Duo IP instances not supported by rm_netxduo_ether.
      • When repeatedly establishing connections using rm_netxduo_ether, support is currently limited to a single Azure RTOS NetX Duo IP instance.
  • TFU:
    • The IAR compiler does not support TFU intrinsic functions for RX74M and RX74N. Therefore, the TFU feature is not available when using the IAR compiler.

Configuration Notes

  • Callback function must be created manually.
  • Ensure the Main Clock Source in the debugger Connection Settings matches the clock configuration in FSP.
  • In FreeRTOS projects:
    • The default FreeRTOS blinky speed is too fast for visual observation; adjust the timer period (e.g., to 1 ms) after adding the timer driver.

Known Issues

  • In CC-RX projects:
  • In GCC projects:
    • Removing a motor module that uses a library, for example rm_motor_estimate, after a successful build may leave its linker archive settings in the project.
    • This may cause the build error “cannot find -lrm_motor_estimate: No such file or directory.”
    • To resolve this issue, manually remove rm_motor_estimate from C/C++ Build > Settings > Tool Settings > Linker > Archives > User defined archive, and remove its path from User defined archive search directories, then rebuild the project.
  • When using IAR Embedded Workbench for RX:
    • Third-party codes warnings are not suppressed. E.g., Variable xx was set but never used.
    • By default, enum types are packed as uint8_t. For interrupt vectors greater than 127, set "enum_is_int" option (Project>Options>C/C++ Compiler>Extra Options) to enforce a minimum enum size of 4 bytes.
    • Builds may hang when a high optimization level is selected.

For the latest status of known issues and available workarounds, please refer to the GitHub Issues page.

ProtectZone

How to Configure the Partition Boundary between Secure and Non-Secure

  1. Click Run - Renesas Debug Tools - Renesas Device Partition Manager on e2 studio as shown below:
DevicePartitionManager_1

  1. When Renesas Device Partition Manager is successfully launched, the following settings are configured:

    • Check Set secure / non-secure boundaries
    • Choose E2 Lite as Target MCU connection
    • Choose SCI as Connection Type:
    • Choose 3.3 as Debugger supply voltage (V):
    • Choose 9600 as Connection Speed (bps for SCI, Hz for SWD)
    • Specify 512 as Code Secure (KB)
    • Specify 24 as Data Secure (KB)
    DevicePartitionManager_2

  2. Click Run to start partitioning. If the boundaries are successfully configured, you can see Partition settings: SUCCESSFUL! as shown below:

    DevicePartitionManager_3

ProtectZone Limitations

  • Secure World supports bare-metal applications only.
  • Non-Secure World supports bare-metal applications and FreeRTOS only.
  • Azure RTOS is not supported.
  • Nested transitions between Secure and Non-Secure worlds are not supported.
  • Automatic Secure Context switching for RTOS tasks is not supported.
  • Big-endian operation is not supported.
  • Group interrupts are supported only in Secure mode. Therefore, peripherals/functions that use the following Group interrupts cannot use these interrupts in Non-secure mode:
    • Group IL0: DPFPU, LM0, CM, BUS, MRAM
    • Group BL0: SDHI, XSPI0, XSPI1, SSIE0, SSIE1, PDC, PDMIF
    • Group BL1: CAC0, CAC1, CAC2
    • Group AL0: RSCI0, RSCI1, RSCI2, RSCI3, RSCI4, RSCI5, RSCI6, RSCI7, RSCI8, RSCI9
    • Group AL1: RSCI10, RSCI11, RSCI12, RIICHS1, RIICHS2, RI3C0, DSMIF0, DSMIF1, RSPIA0, RSPIA1, RSPIA2, DOC
    • Group AL2: CANFDG0, CANFD0, CANFD1, CANFD2 ,CANFD
    • Group AL3: POEG
    • Group AL4: ESWM, ESC
    • Group AL5: ADC

ProtectZone Known Issues

  • Build errors related to undefined external symbol may occur when building a secure application with the CC-RX compiler.
    • To workaround, define the _RX_PZ_SECURE assembler symbol as follows:
      1. From the Project menu, select C/C++ Project Settings of e2 studio, please select Paths and Symbols, then open the Symbols tab.
      2. Under Languages, please select Assembly and click Add.
      3. Please enter _RX_PZ_SECURE in the Name field and 1 in the Value field, then click OK.

Third Party Software

These third party software solutions are included alongside FSP.

Read more
Assets 10
Loading