Skip to main content
V
vignesh1
Associate II
August 22, 2024
Solved

Understanding on Flash Memory Endurance Cycles for STM32 Microcontrollers

  • August 22, 2024
  • 2 replies
  • 3736 views

I’m using an STM32 microcontroller and am trying to understand more about the flash memory endurance cycles. The datasheet mentions an endurance of 1 kcycle (1,000 program/erase cycles). I think possible Write and read  (1000 cycles ) or is there any limits about  program/erase cycles?

Could  explain what exactly this means in terms of practical use? How are these cycles characterized, and what factors might affect the actual endurance in a real-world application?

 

 

 

Thanks!"

    Best answer by TDK

    1 cycle = 1 erase + 1 write.

    That means the chip will work if you erase and program it 1000 times. After that, operation is not guaranteed (but it's likely to continue to work well after that point).

     

    The STM32G0x0 is a budget line. Lots of other families have 10k endurance cycles. If you have an application with lots of writing, perhaps look for a chip with higher endurance, or use an external dedicated FLASH chip.

    2 replies

    TDK
    TDKBest answer
    August 22, 2024

    1 cycle = 1 erase + 1 write.

    That means the chip will work if you erase and program it 1000 times. After that, operation is not guaranteed (but it's likely to continue to work well after that point).

     

    The STM32G0x0 is a budget line. Lots of other families have 10k endurance cycles. If you have an application with lots of writing, perhaps look for a chip with higher endurance, or use an external dedicated FLASH chip.

    "If you feel a post has answered your question, please click ""Accept as Solution""."
    Andrew Neil
    Andrew Neil
    Super User
    August 22, 2024

    It's the erase which causes the wear - not the write or read.

    https://community.st.com/t5/stm32-mcus-embedded-software/issues-with-x-cube-eeprom/m-p/662768

    https://community.st.com/t5/stm32-mcus-products/flash-write-versus-erase-cycles/m-p/665435 

    https://community.st.com/t5/stm32-mcus-products/effect-of-erasing-an-already-erased-flash-page-wear/m-p/677740

    https://community.st.com/t5/stm32-mcus-embedded-software/eeprom-emulation-virtual-addresses/m-p/675788 

     

    @vignesh1 wrote:

    what factors might affect the actual endurance in a real-world application?

    Minimise the amount of erasing!

    A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
      Terms & ConditionsAccessibility statement