If a flash block is read during the execution of an algorithm (FSTAT[CCIF] = 0) on thatsame block, the read operation will return invalid data.If FSTAT[ACCERR] or FSTAT[FPVIOL] are set, the user must clear these fields beforestarting any command write sequence.CAUTIONAn flash longword must be in the erased state before beingprogrammed. Cumulative programming of bits within an flashlongword is not allowed.11.3.10.1 Erase Verify All Blocks commandThe Erase Verify All Blocks command will verify that all flash blocks have been erased.Table 11-11. Erase Verify All Blocks command FCCOB requirementsCCOBIX[2:0] FCCOBHI parameters FCCOBLO parameters000 0x01 Not requiredUpon clearing FSTAT[CCIF] to launch the Erase Verify All Blocks command, thememory controller will verify that the entire flash memory space is erased. TheFSTAT[CCIF] flag will set after the erase verify all blocks operation has completed. If allblocks are not erased, it means blank check failed and both FSTAT[MGSTAT] bits willbe set.Table 11-12. Erase verify all blocks command error handlingRegister Error bit Error conditionFSTATACCERR Set if CCOBIX[2:0] != 000 at command launchFPVIOL NoneMGSTAT1 Set if any errors have been encountered during the read1 or if blank checkfailedMGSTAT0 Set if any errors have been encountered during the read or if blank checkfailed1. As found in the memory map for NVM11.3.10.2 Erase Verify Block commandThe Erase Verify Block command allows the user to verify that an entire flash block hasbeen erased. The FCCOB global address [23:0] bits determine which block must beverified.Chapter 11 Flash Memory Module (FTMRH)MC9S08SU16 Reference Manual, Rev. 5, 4/2017NXP Semiconductors 169