30.2.22 Errors and Flags

Several non-typical events can occur that affect the operation of the FCW causing Write/Erase operations to be aborted. Setup errors can occur that prevent the start of an NVMOP command. All these errors are reported via INTFLAG. Some flags are updated before the FSM clears BUSY. However, the FSM always clears BUSY and sets DONE on the same clock edge.

The following table describes the types of errors the FCW detects and what flags they affect.

Table 30-2. Interrupt Flag Summary
INTFLAGs:	Source:	Effect on FCW Operations:
WRERR, DONE	Any Error Event during NVMOP	Last address programmed may be corrupted, or last erase may not be complete.
RSTERR, DONE	BOR circuit not Ready before NVMOP written	NVMOP not started⁽²⁾ SW should enable BOR and wait for it to be ready.
RSTERR⁽¹⁾	Reset or Low Voltage Event before FSM starts NVMOP	NVMOP not started⁽²⁾
RSTERR⁽¹⁾, WRERR	Reset or Low Voltage Event after FSM starts NVMOP	Last address programmed may be corrupted, or last erase may not be complete. Software should verify results.
HTDPGM, DONE	High Temp Event before FSM starts NVMOP	NVMOP not started⁽²⁾
WRERR, SECERR, DONE	Security module or tamper event preempted operation	Last address programmed may be corrupted, or last erase may not be complete.
KEYERR	KEY not valid for SFR write	SFR not updated
CFGERR, DONE	ADDR not in flash memory space Disallowed CPUDAL setting.	NVMOP is not started ⁽²⁾
CFGERR, OPERR, DONE	NVMOP not allowed because of ECC, i.e. Single Write attempted when ECC Write with ECC Read is selected	NVMOP is not started ⁽²⁾
WRERR, FIFOERR, DONE	Row Write FIFO under run error	NVMOP is aborted⁽²⁾ Subsequent addresses not programmed
BUSERR, FIFOERR⁽³⁾, DONE	AHB Bus Host error before FIFO filled Possible SRCADDR out of range	NVMOP is not started⁽²⁾
BUSERR, FIFOERR⁽³⁾, WRERR, DONE	AHB Bus Host error Possible SRCADDR out of range or access permission violation	NVMOP is aborted⁽²⁾ Current and subsequent addresses not programmed
WPERR, DONE	ADDR is write protected by a WP register (i.e BWP, PWP, etc)	NVMOP is not started⁽²⁾
WPERR, SECERR, DONE	ADDR is write protected by a different security association⁽⁴⁾	NVMOP is not started⁽²⁾
OPERR, DONE	NVMOP is not available (e.g. RSVD)	NVMOP is not started⁽²⁾
SECERR	Security Violation	SFR access blocked Does not generate a bus error
Note: If BOR causes a reset, DONE will not be set because it is cleared by the reset. NVMOP is generally considered started when the panel is enabled. Error code may or may not be set.

The following table summarizes events that cause the Write/Erase sequence to not occur but do not set the error flag.

Table 30-3. Conditions Without an Error Flag
Source:	Effect on FCW Operations:
Writing KEY with an invalid value.	Locks all registers protected by KEY.
Attempted write of an SFR while locked for programming (BUSY=1) from the same security association.	Action is ignored by FSM and SFRs. Reports a bus error.
Attempted read or write of an SFR address that is not implemented.	Action is ignored by FSM and SFRs. Reports a bus error.