Flash failure from Wifi writing credentials about slimevr-tracker-esp HOT 9 CLOSED

@Kamilake No, the board resets if you try to access damaged flash, so credentials can no longer be written. Not sure if it can still be read. Otherwise it appears to work fine

from slimevr-tracker-esp.

Related issue: esp8266/Arduino#1054

from slimevr-tracker-esp.

That's interesting. It doesn't seem to happen on ESP32.

Does that cause the whole board to boot fail? Or does it only corrupt credentials?
Do I(that board) need to Wifi.persistent(false) on every run except when performing a write operation?

from slimevr-tracker-esp.

Similar issue seems to be occurred on Wemos D1 Mini when powered via micro-USB port, but works ok on battery. Though Wifi.persistent(false) didn't help.
https://discord.com/channels/817184208525983775/823930029070876736/905833475741982721

from slimevr-tracker-esp.

Need to review Wifi.begin() code for different frameworks and see how to start wifi properly without it being re-written, but still being able to read it on begin and write on credentials change.

from slimevr-tracker-esp.

On the espressif8266 platform this should not be the case. Only when SSID and the passphrase are provided will Wifi.begin() write to flash if persistence is not set to false. When not providing these parameters it should only read from flash (code below).

wl_status_t ESP8266WiFiSTAClass::begin() {

    if(!WiFi.enableSTA(true)) {
        // enable STA failed
        return WL_CONNECT_FAILED;
    }

    ETS_UART_INTR_DISABLE();
    wifi_station_connect();
    ETS_UART_INTR_ENABLE();

    if(!_useStaticIp) {
        wifi_station_dhcpc_start();
    }
    return status();
}```

from slimevr-tracker-esp.

Can this be closed? Neither esp32 nor esp8266 does any writing to memory when wifi.begin() is called without arguments. (In fact the function does not even reference if persistence is set to true or false in either function.)

from slimevr-tracker-esp.

Did we used to use WiFi.begin(SSID, pass)? Or was this open on error, @Vyolex?

from slimevr-tracker-esp.

IDK if it used to be different but atm we only call WiFi.begin(SSID, pass) in setWiFiCredentials and in upkeep (the latter only when the ssid and pass are defined in code). So default behaviour should not cause data to be written to flash every single boot, only on sending credentials from server.

from slimevr-tracker-esp.