Want to detect the number of times a switch value is used through stm32

[zhaowhong]

Hi 

Because power-off protection is required, the times or variables need to be stored in flash。
Is my solution reasonable?

Create a space inside the flash to define variables, and read the data after powering on the computer. Then there is a problem with data accumulation ， inside the my program the define variables be accumulated， because the data is stored inside the flash. Does the change of data require special processing? HAL_FLASH_Unlock()
How to define variables inside flash, please give a program example。

Thank you

 

[Andrew Neil]

https://community.st.com/t5/stm32-mcus-products/eeprom-emulation/m-p/719118 

https://community.st.com/t5/stm32-mcus-products/flash-memory/m-p/672904

 

[zhaowhong]

To add, this variable of mine changes while the program is running. and needs to be stored in flash

[Andrew Neil]

Yes, that is addressed in the threads I linked.

[Tesla DeLorean]

NVRAM / BKPRAM might be more practical. 

FLASH sectors on the F4 are quite large and time consuming to erase

 You'd need to carve holes to use the smaller 16KB sectors.

You can journal writes across the sector, and the enumerate at next startup to find the last saved data.

[zhaowhong]

YES  

I read some documents that must be erased when writing. I originally planned to use RAM variables to record. And wanted the CPU to write to FLASH before powering off, but the demand is not sure when to power off, and powering off is uncontrollable.

It seems that methods such as external feram are better。

[Andrew Neil]

You haven't said what STM32 you're using.

Some have the facility for battery-backup of a portion of RAM...

 

---

@zhaowhong wrote:

, but the demand is not sure when to power off, and powering off is uncontrollable.

---

So what you'd need is

1. A signal (interrupt?) to tell you when the power had been turned off, and
2. Enough backup/reserve power to be able to complete a flash write.