Configuration parameters in 3.0.12 beta
Posted: 06 Mar 2024 15:43
Hi,
I am currently giving 3.0.12b a try. I have sketch file called eol.ino that stores some stuff in EEPROM and sets the default values for the parameters I use in my main sketch. For some reason, when I use zunoSaveCFGParam() function, no values are getting written to EEPROM. On 3.0.10 it works flawlessly. The only possibility to have default values for parameters saved is to use the macro ZUNO_SETUP_CONFIGPARAMETERS.
But I am wondering if ZUNO_SETUP_CONFIGPARAMETERS is the correct way to proceed. Each time I flash or update my sketch, the parameters will be overwritten. I don't think this is the intended usage for the default value in this macro. Im my opinion, the macro should check for a default written value for a config parameter in EEPROM in production (let's say 0xAFAFAFAF), and only write the default value provided by the macro ZUNO_SETUP_CONFIGPARAMETERS when the config parameter hasn't been set before.
Is this issue known to you?
I am currently giving 3.0.12b a try. I have sketch file called eol.ino that stores some stuff in EEPROM and sets the default values for the parameters I use in my main sketch. For some reason, when I use zunoSaveCFGParam() function, no values are getting written to EEPROM. On 3.0.10 it works flawlessly. The only possibility to have default values for parameters saved is to use the macro ZUNO_SETUP_CONFIGPARAMETERS.
But I am wondering if ZUNO_SETUP_CONFIGPARAMETERS is the correct way to proceed. Each time I flash or update my sketch, the parameters will be overwritten. I don't think this is the intended usage for the default value in this macro. Im my opinion, the macro should check for a default written value for a config parameter in EEPROM in production (let's say 0xAFAFAFAF), and only write the default value provided by the macro ZUNO_SETUP_CONFIGPARAMETERS when the config parameter hasn't been set before.
Is this issue known to you?