Errata Sheet - Infineon

Errata Sheet
Functional Deviations
the erase operations, as described in the following sequence (x, y = 0 or 1,
x ≠ y):
1. A Program Flash sector or a Data Flash sector (DFy or DFx) has been
erased.
2. An erase command on Data Flash sector DFx is issued.
3. While the erase operation on sector DFx is in progress, during a certain
critical time window a programming command on sector DFy is issued, i.e.
the erase operation on sector DFx is suspended.
In other words, potentially critical sequences are:
• Erase PFLASH --> erase DFx --> program DFy (suspend erase DFx), or
• Erase DFy --> erase DFx --> program DFy (suspend erase DFx), or
• Erase DFx --> erase DFx --> program DFy (suspend erase DFx).
As a consequence, sector DFx may not be correctly erased after the suspended
erase has been completed (i.e. DFx may be weakly programmed). The effect is
non-permanent, i.e. erasing DFx again will solve the issue.
Note: Sector DFy is always correctly programmed.
Therefore, both Data Flash sectors or a Program and a Data Flash sector must
not be erased one after the other if the second erase operation might be
suspended.
Workaround 1
Additionally program (a page of) Data Flash sector DFx or DFy, before starting
the erase of DFx, e.g.:
1. Erase PFLASH or DFx or DFy
2. Additional step: Program DFx or DFy (specified rules for Data Flash page
programming must remain valid), check for completion of programming
(busy)
3. ... (any operation except erase of DFx, DFy, or PFLASH)...
4. Erase DFx
5. Concurrent programming of DFy may be triggered.
Workaround 2
After starting the erase of Data Flash sector DFx, delay the start of the
programing of sector DFy by at least 250 ms, e.g.:
TC1767, EES-AD, ES-AD, AD 36/73 Rel. 1.4, 11.12.2009