Saving credentials does not work about configmanager

[nrwiersma]

Hi,

Can you check if this branch works for you. If so I will merge and make a patch release.

[nrwiersma]

Hi,

You are correct. It seems that the EEPROM is not being initialised, even though it should be after ::begin. It could be hardware that is failing here, have you tired on more than 1 ESP32?

[ReneHezser]

Hi,
a second one is behaving exactly the same.
Edit: The "simple" example does the same :-(

[nrwiersma]

Hi,

I would start debugging be running EEPROM:begin() and looking at the bool output, there are logs too. Then run EEPROM:length() and check you get the correct size back.

[ReneHezser]

  Serial.print("eeprom test");
  bool success = EEPROM.begin(0);
  Serial.print(success);
  success = EEPROM.begin(1);
  Serial.print(success);
  uint16_t l = EEPROM.length();
  Serial.print(l);

And the output is:

eeprom test010

[nrwiersma]

Ok,

So digging through the ESP32 EEPROM code, i see the issue. ESP32 has gone a a different way when implementing length than ESP8266. In ESP8266 length tells you the initialised size from begin. In ESP32 it has nothing to do with the size in begin.

I am not sure how to deal with this.

[ReneHezser]

When I commented out lines 379-382, it worked for me.

    // if (EEPROM.length() == 0) {
    //     DebugPrintln(F("WiFi Settings cannot be stored before ConfigManager::begin()"));
    //     return;
    // }

How about a variable that keeps track of the initialization through begin()?

[nrwiersma]

I think i will just disable the check on ESP32. In ESP8266 it is needed to check that EEPROM was actually initialised. Apparently we cannot do that on ESP32.

[ReneHezser]

Thank you. Strange the ESP32 does need special treatment. With this change it does work again.