R01US0079ED0103 Datasheet, PDF (58/66 Pages) Renesas Technology Corp – RENESAS 32-Bit MCU

Data Flash Access Library - Type T01, European Release
Library Setup and Usage
5.3 Library resources
5.3.1 Linker sections
The following sections are related to the Data Flash Access Library and need to be defined in the linker
file (please see sample linker directive file for an example):
Data sections:
 R_FDL_DATA
This section contains all FDL internal variables. It can be located either in internal or external RAM.
Code sections:
 R_FDL_CONST
This section contains library internal constant data. It can be located anywhere in the code flash.
 R_FDL_TEXT
FDL code section containing the library code. It can be located anywhere in the code flash.
5.3.2 Stack and Data Buffer
The FDL utilizes the same stack as specified in the user application. It is the developer’s duty to reserve
enough stack for the operation of both, user application and FDL. With source code library it is not
possible to give an exact value for stack consumption. However, an estimate value for the FDL library is:
268 bytes for GHS compiler and 316 bytes for Renesas compiler.
The data buffer used by the FDL refers to the RAM area in which data is located that is to be written into
the data flash. This buffer needs to be allocated and managed by the user.
Note:
In order to allocate the stack and data buffer to a user-specified address, please utilize the link directives
of your framework.
5.4 MISRA Compliance
The FDL code has been tested regarding MISRA^TM compliance.
The used tool is the QA C^TM Source Code Analyzer which tests against the MISRA^TM 2004 standard rules.
Note:
"MISRA" is a registered trademark of MIRA Ltd, held on behalf of the MISRA Consortium.
“QA C” is a registered trademark of Programming Research Ltd.
5.5 Sample Application
It is very important to have theoretic background about the Data Flash and the FDL in order to
successfully implement the library into the user application. Therefore it is important to read this user
manual in advance. The best way, after initial reading of the user manual, will be testing the FDL
application sample.
After a first compile run, it will be worth playing around with the library in the debugger. By that you will get
a feeling for the source code files and the working mechanism of the library. After this exercise it might be
easier to understand and follow the recommendations and considerations of this document.
R01US0079ED0103
58
User Manual