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

Data Flash Access Library - Type T01, European Release
User Interface (API)
Status
Background and Handling
reason
 To gain robustness, the parameter check is repeated
right before Flash modification and returns the
protection error in case of a violation (e.g. due to an
unwanted variable modification)
 Other device specific protection mechanisms (e.g.
security unit like ICU or FHVE protection mechanisms
prevent Flash operations.
remedy
Refrain from further Flash operations and investigate in the
root cause
meaning Current command is rejected
R_FDL_ERR_REJECTED⁽²⁾
reason
remedy
Another operation is ongoing
Request again the command when the preceding
command has finished
meaning At least one data could not be written correctly
R_FDL_ERR_WRITE⁽¹⁾
reason
 User flow defect: tried to “overwrite” data (write into
non-erased cells)
 Hardware defect: one or more Flash bits could not be
written
remedy
Erase write area before writing.
A Flash block respectively the complete Data Flash should
be considered as defect
meaning
A library internal error occurred, which could not happen in
case of normal application execution
R_FDL_ERR_INTERNAL⁽¹⁾
reason
 Application bug (e.g. program run-away, destroyed
program counter) or hardware problem
 Only on older F1x devices: failed ID code
authentication supplied in the device descriptor. See
section 4.2 ”Run-time configuration” for details about
ID code
remedy
Refrain from further Flash operations and investigate in the
root cause
(1) _{R_FDL_Execute will never set this status code}
(2) _{R_FDL_Handler will never set this status code}
4.5.3 R_FDL_CMD_BLANKCHECK
The blank check command can be used by the requester to check whether a specified amount of memory
starting from a specified address is written. This command will stop at the first memory location that is not
erased with status R_FDL_ERR_BLANKCHECK.
Notes:
1. On blank check fail, the cells are surely not blank. This might result from successfully written cells, but
also from interrupted erase or write operations.
2. On blank check pass, the cells are surely not written. This might result from successfully erased cells,
but also from interrupted erase or write operations.
3. Depending on the Flash operations use case (e.g. EEPROM emulation) it may be necessary to log
the Flash operations results in order to be sure that Flash cells are correctly written or erased. The
way of logging depends on the use case (e.g. as part of a EEPROM Emulation concept)
R01US0079ED0103
48
User Manual