TC1784
Program Memory Unit (PMU)
User´s Manual
5-84
V1.1, 2011-05
PMU, V1.47
•
Wordline oriented fails can also have the effect that the affected wordlines can not be
erased anymore (other wordlines stay fully functional). A robust EEPROM emulation
is immune against such wordlines (e.g. by identifying old data by version counters).
For the TC1784 this robust EEPROM algorithm is required for the usage of the DFlash.
Due to the specificity of each application the appropriate usage and implementation of
these measures (together with the more elaborate VER handling) must be chosen
according to the context of the application.
5.6.6.4
Handling Errors During Startup
The FSR flags are not only used to inform about the success of Flash command
sequences but they are also used to inform (1) the startup software and (2) the user
software about special situations incurred during startup. In order to react on this
information these flags must be evaluated after reset before performing any flag clearing
sequence as “Clear Status” or “Reset to Read”.
The following two levels of situations are separated:
•
Fatal level: the user software is not started. A WDT reset is performed.
•
Error level: the user software is started but the Flash memory must not be
programmed or erased.
•
Warning level: the user software is started but a warning is issued.
Fatal Level (WDT Reset)
These error conditions are evaluated by the startup software which decides that the
Flash is not operable and thus waits for a WDT reset. The application sees only a longer
startup time followed by a WDT reset.
The reason for a failed Flash startup can be a hardware error or damaged configuration
data.
Error Level (Flash Read-Only)
In this condition the user software is started but the Flash memory must not be
programmed or erased. If writability of the Flash is mandatory the user software itself has
to perform a reset.
Flash microcode error:
FSR bits set: PFOPER and DFOPER.
The user software is started normally but the Flash must not be programmed or erased.
Please note that programming or erasing is not blocked by hardware. Issuing program
or erase sequences despite this condition is forbidden.
Summary of Contents for TC1784
Page 1: ...User s Manual V1 1 2011 05 Microcontrollers TC1784 32 Bit Single Chip Microcontroller ...
Page 3: ...User s Manual V1 1 2011 05 Microcontrollers TC1784 32 Bit Single Chip Microcontroller ...
Page 950: ...TC1784 Direct Memory Access Controller DMA User s Manual 11 132 V1 1 2011 05 DMA V3 03 ...
Page 1949: ...TC1784 General Purpose Timer Array GPTA v5 User s Manual 21 297 V1 1 2011 05 GPTA v5 V1 14 ...
Page 2350: ...w w w i n f i n e o n c o m Published by Infineon Technologies AG Doc_Number ...