7064 - MachXO2: Why MachXO2 device internal flash (CFG/UFM) is not fully erase with typical tEraseCFG, tEraseUFM wait cycle when using Embedded Programming.

7064 - MachXO2: Why MachXO2 device internal flash (CFG/UFM) is not fully erase with typical tEraseCFG, tEraseUFM wait cycle when using Embedded Programming.

There is 2 methods to confidently ensure ERASE cycle is completed for MachXO2 with Embedded Programming.

1. Follow tErase(max) specification for Erase wait cycle. By following tErase(max) spec, user can ensure that the device will be fully erased.
2. Alternately, user may poll the Busy bit in the status register to confirm the Erase is done.
   

1. tErase (typ min/max) = normal distribution of the flash’s characteristics
2. tErase(max) = absolute time to wait for the Erase to be complete