is there a #define symbol for the first really free EEPROM address ?

[GertSanders]

is there a #define symbol for the first really free EEPROM address ?

From the .h file I gather that EEPROM_LOCAL_CONFIG_ADDRESS and higher are free of my own use ???

[mfalkvidd]

@gertsanders yes that's correct. From the documentation:

First free address for sketch static configuration.

But whenever a new version of the MySensors library needs more eeprom, EEPROM_LOCAL_CONFIG_ADDRESS will be changed. So be careful when upgrading the library.

https://github.com/mysensors/MySensors/issues/379 has been created to make the address more permanent.

I am not sure which addresses saveState/loadState uses. Maybe that function is more resilient.

EDIT: saveState uses EEPROM_LOCAL_CONFIG_ADDRESS internally, so saveState will be broken as well if the library changes EEPROM_LOCAL_CONFIG_ADDRESS. But do use saveState instead of writing directly to the eeprom.

[alowhum]

@mfalkvidd said in is there a #define symbol for the first really free EEPROM address ?:

https://github.com/mysensors/MySensors/issues/379

I would like to store some strings in eeprom.

The nodes will also use the awesome simple security feature (signing, encryption). I suspect those also write some things to eeprom (I did research this just now, but I wasn't able to find anything on it).

Combining all that: would it be smart to just start the storage of these string 'further down', like at 256? As far as I can tell all arduino's have at least 512bytes of eeprom, so then MySensors can still expand into the first 256 in the future, but my code will still be fine?