The Nano Classic an also Nano Every has a couple of EEPROM. The other new types
for SAMD (33 IoT) GitHub - cmaglie/FlashStorage: A convenient way to store data into Flash memory on the ATSAMD21 and ATSAMD51 processor family
Thank you - but sorry, it doesn't help for me. In the readme.md is a question with a very exact answer:
Q: The content of the FlashStorage is erased each time a new sketch is uploaded?
A: Yes, every time you upload a new sketch, the previous content of the FlashStorage is erased.
During program optimisation there are some new uploads...
When I have stored some value pairs, they should stay permanently - even like an EEPROM.
The ESP8266 people have a solution, it looks like a special file, available also after reset/powerup and upload a new sketch.
RudolfAtRTC:
Thank you - but sorry, it doesn't help for me. In the readme.md is a question with a very exact answer:Q: The content of the FlashStorage is erased each time a new sketch is uploaded?
A: Yes, every time you upload a new sketch, the previous content of the FlashStorage is erased.During program optimisation there are some new uploads...
When I have stored some value pairs, they should stay permanently - even like an EEPROM.
The ESP8266 people have a solution, it looks like a special file, available also after reset/powerup and upload a new sketch.
the source of the Q&A?
OK - very simple: I followed your link (to Github cmaglie/FlashStorage). In the "readme.md" there is a chapter "FAQ" with this question/answer.
the library is half-baked. the EEPROM emulation should be in a region of flash which can be protected by the EEPROM fuse
What about the "Nano 33 BLE Sense", is there any library for EEPROM emulation? or at least a project to write any?
That would be great...
https://community.atmel.com/forum/samd21-eeprom-emulator-service-non-volatile-memory
it seems that the EEPROM Emulation which uses flash is erased (not preserved) when you flash the chip. I was able to confirm this with the following code. I searched through the documentation and didn't see this referenced. Turns out that I missed this setting: To preserve code DESELECT
If I deselect it, my data is preserved. Makes sense... wish it was in the documentation
@ttbooysen, please explain the purpose of your reply.
I see it's just a copy/paste of the reply from https://community.atmel.com/comment/1937676#comment-1937676
Was it your intention to repost this to add some helpful information to this thread, or are you a bot that did this automatically to prep a spam account? If you don't respond, I'll assume the latter and act accordingly.