I have found the problem. It's due to setting the board type as ESP32-WROOM-DA when it is not a dual antenna board. The dual antenna boards use gpio 2 for antenna 1 so selecting this board causes the on board LED to go crazy.

The fix is to change the board to "ESP32 Dev Kit".

Thanks

That was indeed the problem. I had not realised that the DA stands for Dual Antenna, and with dual antenna gpio 2 is used for antenna 1. Changing the board to "ESP32 Dev Kit" has indeed fixed the problem.

Thanks, but the LED flashes in the same way even if I use this program:

#include <WiFi.h>

#define MY_SSID "foo"
#define MY_PWD "bar"

void setup() {
WiFi.begin(MY_SSID, MY_PWD);
}

void loop() {
delay(1000);
}

I have uploaded a video to show how the LED starts flashing as soon as WiFi.begin ...

A rather late reply, but I have a similar problem. I haven't found any way to stop WiFi.begin() from messing with the builtin LED, but I managed to get the WiFi enabled using just the ESP API. This code enables the WiFi without affecting the built in LED:

#include <WiFi.h>
#include "esp_system.h ...

Thanks, but that is not what I'm asking.

It seems like the WiFi object already does does something similar to what you suggest. If I turn on the WiFi using:

void connectWiFi() {
WiFi.begin(MY_SSID, MY_PWD, 6);
int loopcnt = 0;
while (WiFi.status() != WL_CONNECTED) {
Serial.printf("%d WiFi ...

I have a generic ESP32-WROOM-32D dev board that I'm using to learn ESP32 programming using the Arduino IDE. I've noticed that when I use the WiFi object from WiFi.h the built in LED illuminates to show the state of the connection. When I call WiFi.begin() the LED turns on solid, then once the WiFi ...

Thanks again.

It turns out you can use sockets even in Arduino mode. If anyone is interested, this code works:

#include <lwip/sockets.h>
#include "WiFi.h"

void ConnectWiFi() {
WiFi.begin("myssid", "mypassword", 6);
int loopcnt = 0;
while (WiFi.status() != WL_CONNECTED) {
Serial.printf ...

Thanks

A delay will certainly stop the task calling WiFiServer.available() from using 100% CPU so that would be a solution, but is there no way to make WiFiServer.available() block?

Solved. I needed to #include "esp32/rom/gpio.h". Apparently this changed going from v2 to v3.

-------------------------------------------------------------------------------------------------------------------

Thanks for posting this :-)

When I try to compile it I get errors:

D:\rhs\ESP32 ...

In unix we would typically code a server using something like:

listen(sock_srv, 1);
while (true) {
sockaddr addr_client;
int sock_client = accept(sock_srv, &addr_client, NULL);

The call to accept() blocks until a connection is received, at which point it springs back into life and returns a ...