This page is for know issues and possible workarounds for RA MCU software, tools, and boards.
Here are some of the known RA/FSP issues and possible workarounds.
MCUboot is a secure bootloader for RA MCUs which includes a flash layout to enables the software update. The Flash layout determines the flash size for the bootloader area and the primary/secondary image slot area.
A typical MCUboot application consists of MCUboot project, and a primary Application and secondary image for the update. When MCUboot project is created, a Flash layout .bld file is generated by FSP Code generator based on the MCUboot stack configuration as below. The generated .bld file is added in the debug\exe folder of the project.
In e2Studio IDE, a tooling is included in which an application project can pick up the bootloader project flash layout settings from .bld file. However, for IAR workbench manual work is needed to pick up the bootloader project flash layout settings. This requires modifying the memory mapping file “memory_regions.icf” file for the application project manually. However, when the code is build, FSP code generator is invoked which overwrites the “memory_regions.icf file. Hence, it is must to change the file property to read only after modification to avoid over writing the file when code is regenerated.
Here is an example of the .bld file from RA6M3 MCUboot project and then corresponding modification in memory_regions.icf file which includes adding the Flash image start and end location.
Please note be aware that when if the memory_regions.icf file is made set to read-only and you attempt to build the project is build in IAR workbench, there is Workbench, you will encounter a "Usage Error" error message pops up as “Error pop window stating "Error generating project content” content" as shown below. This is mainly issue occurs because the RA Smart Configurator (RASC) can't overwrite “memorycannot overwrite the memory_regions.icf” file and icf file. The error message is not assciated with related to any issue issues with the application project. In order to To resolve this error, it is required to close the "Usage Error" window, which will then continue allow the build process to continue and complete the remaining build operation. . If project has any issues, the error message will be shown in the "Build" output window of the IDE.
Table of Contents |
---|