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

Data Flash Access Library - Type T01, European Release
User Interface (API)
4. Internally blankcheck operation is split into smaller operations every time the operation crosses a
0x4000 bytes boundary. This means that time to suspend is not going to exceed the time to fully
perform a blankcheck on 0x4000 bytes.
The members of the request structure given to R_FDL_Execute are described in the following table:
Table 7: Request structure usage for blank check command
Structure member
command_enu
bufAddr_u32
idx_u32
cnt_u16
accessType_enu
status_enu
Value
R_FDL_CMD_BLANKCHECK
-
{uint32_t number}
{uint16_t number}
R_FDL_ACCESS_USER /
R_FDL_ACCESS_EEL
-
Description
Request a blank check operation
Not used
Input: The virtual start address for performing
blank check in data flash. Must be word (4
bytes) aligned.
Output: Fail address in case of blank check
error, unchanged if the operation finishes with
R_FDL_OK.
Number of words (4 bytes) to check
Selects the Flash pool in which the command
will be able to operate.
This is an output member. It contains the
status of the operation during and after the
execution. Possible values are described in
the next table.
The following table describes all possible status returns:
Table 8: Blank check operation returned status
Status
Background and Handling
meaning _{Operation started successfully}
R_FDL_BUSY
R_FDL_OK⁽¹⁾
reason _{No problems during execution}
remedy
meaning
Call R_FDL_Handler until the Flash operation is finished,
reported by the request structure status return value
Operation finished successfully
reason _{No problems during execution}
remedy _Nothing
meaning _{An on-going Flash operation was successfully suspended}
R_FDL_SUSPENDED⁽¹⁾
R_FDL_ERR_PARAMETER⁽²⁾
reason _{Suspend processing successfully finished}
remedy ^{Start another operation or resume the suspended}
operation
meaning _{Current command is rejected}
R01US0079ED0103
49
User Manual