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

Fix erase size in ESP.eraseConfig #3635

Merged
merged 1 commit into from
Oct 15, 2017
Merged

Fix erase size in ESP.eraseConfig #3635

merged 1 commit into from
Oct 15, 2017

Conversation

igrr
Copy link
Member

@igrr igrr commented Sep 22, 2017

SDK uses final 4 sectors of flash for configuration data.
ESP.eraseConfig would only erase 2 sectors, so in some cases of
corrupted data ("system param error"), users could not fix the issue
using ESP.eraseConfig, and had to use esptool instead.

Thanks @HugoML for reporting this.

SDK uses final 4 sectors of flash for configuration data.
ESP.eraseConfig would only erase 2 sectors, so in some cases of
corrupted data ("system param error"), users could not fix the issue
using ESP.eraseConfig, and had to use esptool instead.

Thanks @HugoML for reporting this.
@tablatronix
Copy link
Contributor

tablatronix commented Oct 29, 2017

What is stored in first 2 sectors(first or last?) Because I cannot see any effect from eraseConfig at all in 1.5.3, or at least I see no change in opmode_default or STA SSID, password.

However, This patch seems to work for 2_3_0/1.5.3, not sure how one would do semantic version comparisons to polyfill it, hmm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants