Example for FSP v6.4.0 (1)
Release Notes
Supported FSP version
Example for FSP v6.4.0
Supported Toolchains
e2studio Integrated Development Environment with GCC ARM embedded tool-chain
Keil MDK with ARM compiler tool-chain
IAR EWARM with IAR tool-chain for ARM
New Additions
Application Projects
- Add Renesas RA Family Modbus Sample Program Package for RA8T2 and RA8M2 (r01an8166)
Example Projects
- Added example projects for FPB_RA0E3 (new). Please refer to the example projects document included in the attached bundle for information on supported modules.
Supported Kits
- FPB_RA0E3
Example Projects
Example Projects on GCC:
FPB_RA0E3 --> 13 EP
Example Projects on Keil & IAR:
FPB_RA0E3 --> 1 EPs
Known Issues
-
Clone ra-fsp-examples repository in Windows will be failed due to longpath issue. Please enable longpaths configuration before clone.
git config --global core.longpaths true
Application Projects
-
Some project can fail in building due to long path issue. Please choose "Copy projects into workspace" when import for these projects.
Import → General → Existing Projects into Workspace → Choose the project need to import → Choose "Copy projects into workspace".
Example Projects
-
EK_RA6E2 -> qspi (need to run after FileX_block_media_qspi_LevelX EP)
-
EK_RA8M1, EK_RA8D1, MCK_RA8T1 -> USBX_phid (there is issue with PC/Laptop installed CrowdStrike tool)
-
AWS Example projects: can meet building issue "No rule to make target" due to long path location.
Need to move project folder to shorter location (Ex. D:/). -
FPB_RA0E1 -> all example projects on GCC (use e2studio) are using optimization: -Oz (aggressive size optimization). To override this behavior, manually add the desired optimization flag(s) (e.g. -O0) to the 'Other optimization flags' box in the project Properties. It was reported in https://github.com/renesas/fsp/releases - Known Issues
-
EK_RA8D1, EK_RA8M1 -> USBX_huvc: Example run failed randomly in option 1 (Start record video) with Error code: 0x23.
-
FPB_RA0E3 -> icu (Keil): Cannot detect device when downloading or debugging the project. This issue occurs because the SEGGER J-Link version bundled with Keil is not compatible. To fix the issue, update to a compatible SEGGER J-Link version for Keil MDK-ARM using SEGGER J-Link DLL Updater.