Wifi serial error
E (220) spi RAM enabled but initialisation failed. bailing out
What does this mean?
Can you provide a few more details.
- Which code are you using (Module and Unit)?
- What’s your board?
- When does that error happens (what’s happening before that error)?
- Does your code compile and upload to the ESP32?
I copied and pasted your code module 4 Unit 5 into Arduino IDE, changed my SSID and Passcode. My board is a ESP32 Devkit. I see no other error message. It does download when I hold boot and press EN. Here is the Serial monitor view:
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
mode:DIO, clock div:1
E (220) spiram: SPI RAM enabled but initialization failed. Bailing out.
Connecting to Coetser
My browsers (chrome, firefox, edge) lose connection with my Node MCU 36 pin board after a few minutes (less than ten). even though I can see “espressif” as an active device connected on my router (with identified IP and MAC addresses). If I momentarily disconnect the Node Mcu Esp36 and reconnect it, the browsers read the ESP Web Server page and the buttons work. How would I troubleshoot what is causing the browsers to not to be able to reach the ESP server after a short period of time?
Hello @Chris Coetser, and @Thomas Perillo,
I was able to find a solution for the “new client” error. The web server should now be stable and no longer crash with the second client on Google Chrome. Here’s how to fix your web server:
Please continue the discussion in the new thread (or create a new one), if that solution doesn’t work for any of you.
In my case The addition of 2 second timeout did solve my problem. It seems that when a new client logs in and out without selecting anything the server would just hang. I have it running now with led on output and so far no hanging. In my home there are a couple of wifi users and bandwith may have been my issue.
Keep up the good work!
I’m glad it’s working now. This problem only happens with Google Chrome. Basically, when you access the web server it loads the web page fine. However, for some reason Google Chrome makes an extra request to the web server and leaves the connection open (causing the crash/blocking new clients). With the timeout, it’s very reliable and any client will be disconnected after 2 seconds (you might increase the timeout time if necessary).
Let me know if you experience any other problems. Thanks,
Nice detective work and fix. I have three browsers (Chrome, Firefox, Edge) accessing the web page and executing the on/off flawlessly for most of the morning. Thanks for the fix.