TC1796
System Units (Vol. 1 of 2)
Program Memory Unit
User’s Manual
7-21
V2.0, 2007-07
PMU, V2.0
With the last cycle of the Erase Sector command, Command Mode is entered and the
following status flags are updated:
•
FSR.ERASE is set, indicating that a erase operation is running.
•
Either FSR.PBUSY or FSR.D0BUSY or FSR.D1BUSY is set, indicating that an erase
operation is running in PFLASH or in DFLASH bank 0 or in DFLASH bank 1.
The start of sector erase operation is delayed if the Erase Sector command was issued
to one DFLASH bank while the other DFLASH bank is busy with a program operation.
Read accesses to a DFLASH bank that is currently not erased or programmed are
possible while the other DFLASH bank is erased or programmed. A read access to a
busy (erasing or programming) Flash bank is allowed but delayed until the
corresponding Flash bank is no longer busy. Note that in this case the read path (PLMB)
is completely locked. Therefore, reading from a Flash bank in erase or program state
should be avoided by first polling the busy flags in the FSR register.
If the Erase Sector operation is used to erase a physical sector of the program Flash
(PPS0 or PPS1), this operation is executed only if none of the four sectors within the
related physical sector is write-protected, and if no read protection is installed, or if Flash
protection is disabled.
If read protection and/or write protection for the sector to be erased is enabled, or if one
or more of the sectors within the physical sector to be erased is OTP-protected, the
protection error flag FSR.PROER is set, Command Mode is not entered, and the erase
operation is not started.