Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move EEPROM_LOCAL_CONFIG_ADDRESS to end of EEPROM #379

Open
henrikekblad opened this Issue Jan 30, 2016 · 4 comments

Comments

Projects
6 participants
@henrikekblad
Copy link
Member

henrikekblad commented Jan 30, 2016

We should move the user/local config are to end end of EEPROM so we safely can add new internal configurations without affecting/shifting the local config.

@fallberg fallberg added this to the 2.0.0 milestone Feb 1, 2016

@fallberg fallberg added the enhancement label Feb 1, 2016

@tekka007 tekka007 modified the milestones: 3.0.0, 2.0.0 Jun 19, 2016

@fallberg fallberg added this to TODO in 3.0.0 Feb 27, 2017

@d00616

This comment has been minimized.

Copy link
Contributor

d00616 commented May 2, 2017

If the "end of EEPROM" is the highest available cell address, there is a problem with the NVRAM class. The highest written cell determines the possible change log size.

A smaller change log stands for more page erase cycles. This means to shorten the lifetime of the internal flash memory. I don't know how often the EEPROM is written. In this situation 10,000,000 writes are available.

The NVRAM emulates 3072 bytes. It could be an option move the EEPROM_LOCAL_CONFIG_ADDRESS to 1k.

@fallberg fallberg removed this from the 3.0.0 milestone Feb 25, 2018

@mfalkvidd

This comment has been minimized.

Copy link
Contributor

mfalkvidd commented May 20, 2018

Maybe saveState/loadState could take care of changes to EEPROM_LOCAL_CONFIG_ADDRESS internally instead?

@flatsiedatsie

This comment has been minimized.

Copy link

flatsiedatsie commented Feb 25, 2019

I am running into this issue with the 433 signal cloner. It stores a lot of signal data in eeprom. But because I want it to be safe for users to upgrade to a new version of MySensors without losing their recordings, I am now starting the recordings at the halfway mark of the eeprom, at position 512.

With the MY_SIMPLE_SECURITY option the eeprom claims to be empty from position 413 onwards. So 99 bytes will stay unused. That's "99 problems, but it's not big ones".

Still, if there was a way of grabbing it, it would be nice.

@mfalkvidd

This comment has been minimized.

Copy link
Contributor

mfalkvidd commented Feb 25, 2019

For your use case, why can't you start right at the end of the security stuff?
Or maybe my question is; how would it be safer to use the remaining 99 bytes if the local config address was moved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.