SPIFFS failed!. Please use LittleFS or EEPROM. Stay forever
Petermarcu opened this issue · comments
Describe the bug
I am trying to run the example Async_ConfigOnStartup on my ESP32_DEV board and hit the "SPIFFS failed!. Please use LittleFS or EEPROM. Stay forever" error. I'm hoping you can point me in the right direction to debug further or someone might know what I'm doing wrong.
Steps to Reproduce
Run Async_ConfigOnStartup example on ESP32_DEV board
Expected behavior
AP becomes visible when scanning from my browser enabled device.
Actual behavior
I noticed that it is never getting to the point of setting up the AP. When I open the serial monitor and hard reset the device, I see this error.
Starting Async_ConfigOnStartup using FFat on ESP32_DEV
ESPAsync_WiFiManager v1.12.2
SPIFFS/LittleFS failed! Already tried formatting.
SPIFFS failed!. Please use LittleFS or EEPROM. Stay forever
Information
I just installed all the latest of everything. Arduino IDE, libraries. Running on Windows.
Hi @Petermarcu
Sorry I can't duplicate your issue.
Starting Async_ConfigOnStartup using LittleFS on ESP32_DEV
ESPAsync_WiFiManager v1.12.2
[WM] RFC925 Hostname = AsyncConfigOnStartup
[WM] Set CORS Header to : Your Access-Control-Allow-Origin
ESP Self-Stored: SSID = HueNet1, Pass = 12345678
Opening configuration portal.
[WM] * Add SSID = HueNet1 , PW = 12345678
Got ESP Self-Stored Credentials. Timeout 120s for Config Portal
[WM] LoadWiFiCfgFile
[WM] failed
Open Config Portal without Timeout: No stored Credentials.
Starting configuration portal @ 192.168.4.1, SSID = ESP_9ABF498, PWD = your_password
[WM]
Configuring AP SSID = ESP_9ABF498
[WM] AP PWD = your_password
[WM] AP Channel = 3
[WM] AP IP address = 192.168.4.1
[WM] HTTP server started
[WM] startConfigPortal : Enter loop
[WM] Request redirected to captive portal
[WM] Location http:// 192.168.4.1
[WM] Request redirected to captive portal
[WM] Location http:// 192.168.4.1
[WM] Request redirected to captive portal
[WM] Location http:// 192.168.4.1
[WM] Request redirected to captive portal
[WM] Location http:// 0.0.0.0
[WM] Request redirected to captive portal
[WM] Location http:// 192.168.4.1
[WM] Can't use Custom STA IP/GW/Subnet
[WM] Connected after waiting (s) : 1.30
[WM] Local ip = 192.168.2.109
[WM] Timed out connection result: WL_CONNECTED
WiFi connected...yeey :)
[WM] * Add SSID = HueNet1 , PW = 12345678
[WM] * Add SSID = HueNet2 , PW = 12345678
[WM] getSTAStaticIPConfig
[WM] SaveWiFiCfgFile
[WM] stationIP = 0.0.0.0 , gatewayIP = 192.168.2.1
[WM] netMask = 255.255.255.0
[WM] dns1IP = 192.168.2.1 , dns2IP = 8.8.8.8
[WM] OK
After waiting 0.00 secs more in setup(), connection result is connected. Local IP: 192.168.2.109
[WM] freeing allocated params!
H
You have to check, step-by-step
- your hardware
- update to ESP32 core v2.0.3 (it seems you're using old ESP32 core)
- test littlefs / file system to be sure OK before using this library
I suggest next time you post the problem on Discussions, not Issues if it is not a bug of the library.
I'm closing the issue now as not a bug.
Good Luck,
Thanks. Will do that next time and will follow your suggestions.
FYI - The version of the ESP32 core was the issue. Glad you noticed that. I didn't realize that the package config I was using wasn't the latest. It only had versions up to 1.0.6. After updating to 2.0.3 things just worked.
Thanks for your info which will help many other users to avoid the same issue.
Regards,
How do i update esp32 core in platformio?
Check
- PlatformIO OSS July Updates: PlatformIO Core 6.1, New boards & dev-kits, Arduino Core for ESP32 v2.0.4 and Teensyduino v1.57
- Change arduino-esp32 core version
- PlatformIO Open Source July Updates
There are many more answered issues about this on the PIO Forum