esp-idf: Unable to connect to WiFi, ESP32S3 goes in loop (IDFGH-7755)

Environment

  • Development Kit: ESP32S3-DevKitC
  • Kit version (for WroverKit/PicoKit/DevKitC): v1
  • Module or chip used: ESP32-S3-WROOM-1
  • IDF version (run git describe --tags to find it): v4.4.1
  • Build System: idf.py
  • Compiler version (run xtensa-esp32-elf-gcc --version to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2-patch3) 8.4.0
  • Operating System: MAC
  • (Windows only) environment type: ESP Command Prompt
  • Using an IDE?: No
  • Power Supply: USB

Problem Description

Unable to connect to WiFi using a modified example in /examples/wifi/getting_started/station

Expected Behavior

ESP32S3 should connect to AP

Actual Behavior

ESP32 does not connect to AP. It goes is series of loop Screenshot 2022-07-06 at 16 19 24

Steps to reproduce

  1. Execute esptool.py --chip esp32s3 erase_flash
  2. Go to /examples/wifi/getting_started/station
  3. Compile the example with few modifications:
/* WiFi station Example

   This example code is in the Public Domain (or CC0 licensed, at your option.)

   Unless required by applicable law or agreed to in writing, this
   software is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
   CONDITIONS OF ANY KIND, either express or implied.
*/
#include <string.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "freertos/event_groups.h"
#include "esp_system.h"
#include "esp_wifi.h"
#include "esp_event.h"
#include "esp_log.h"
#include "nvs_flash.h"

#include "lwip/err.h"
#include "lwip/sys.h"

/* The examples use WiFi configuration that you can set via project configuration menu

   If you'd rather not, just change the below entries to strings with
   the config you want - ie #define EXAMPLE_WIFI_SSID "mywifissid"
*/
#define EXAMPLE_ESP_WIFI_SSID      CONFIG_ESP_WIFI_SSID
#define EXAMPLE_ESP_WIFI_PASS      CONFIG_ESP_WIFI_PASSWORD
#define EXAMPLE_ESP_MAXIMUM_RETRY  CONFIG_ESP_MAXIMUM_RETRY

/* FreeRTOS event group to signal when we are connected*/
static EventGroupHandle_t s_wifi_event_group;

/* The event group allows multiple bits for each event, but we only care about two events:
 * - we are connected to the AP with an IP
 * - we failed to connect after the maximum amount of retries */
#define WIFI_CONNECTED_BIT BIT0
#define WIFI_FAIL_BIT      BIT1

static const char *TAG = "wifi station";

static int s_retry_num = 0;

static void event_handler(void* arg, esp_event_base_t event_base,
                                int32_t event_id, void* event_data)
{
    if (event_base == WIFI_EVENT && event_id == WIFI_EVENT_STA_START) {
        esp_wifi_connect();
    } else if (event_base == WIFI_EVENT && event_id == WIFI_EVENT_STA_DISCONNECTED) {
        if (s_retry_num < EXAMPLE_ESP_MAXIMUM_RETRY) {
            esp_wifi_connect();
            s_retry_num++;
            ESP_LOGI(TAG, "retry to connect to the AP");
        } else {
            xEventGroupSetBits(s_wifi_event_group, WIFI_FAIL_BIT);
        }
        ESP_LOGI(TAG,"connect to the AP fail");
    } else if (event_base == IP_EVENT && event_id == IP_EVENT_STA_GOT_IP) {
        ip_event_got_ip_t* event = (ip_event_got_ip_t*) event_data;
        ESP_LOGI(TAG, "got ip:" IPSTR, IP2STR(&event->ip_info.ip));
        s_retry_num = 0;
        xEventGroupSetBits(s_wifi_event_group, WIFI_CONNECTED_BIT);
    }
    else if(event_base == WIFI_EVENT) { // FMOD
        ESP_LOGE(TAG, "Unhandled WIFI_EVENT event_id = %d", event_id);
    }
    else if(event_base == IP_EVENT) { // FMOD
        ESP_LOGE(TAG, "Unhandled IP_EVENT event_id = %d", event_id);
    }
}

void wifi_init_sta(void)
{
    s_wifi_event_group = xEventGroupCreate();

    ESP_ERROR_CHECK(esp_netif_init());

    ESP_ERROR_CHECK(esp_event_loop_create_default());
    esp_netif_create_default_wifi_sta();

    wifi_init_config_t cfg = WIFI_INIT_CONFIG_DEFAULT();
    ESP_ERROR_CHECK(esp_wifi_init(&cfg));

    esp_event_handler_instance_t instance_any_id;
    esp_event_handler_instance_t instance_got_ip;
    ESP_ERROR_CHECK(esp_event_handler_instance_register(WIFI_EVENT,
                                                        ESP_EVENT_ANY_ID,
                                                        &event_handler,
                                                        NULL,
                                                        &instance_any_id));
    ESP_ERROR_CHECK(esp_event_handler_instance_register(IP_EVENT,
                                                        IP_EVENT_STA_GOT_IP,
                                                        &event_handler,
                                                        NULL,
                                                        &instance_got_ip));

    wifi_config_t wifi_config = {
        .sta = {
            .ssid = EXAMPLE_ESP_WIFI_SSID,
            .password = EXAMPLE_ESP_WIFI_PASS,
            /* Setting a password implies station will connect to all security modes including WEP/WPA.
             * However these modes are deprecated and not advisable to be used. Incase your Access point
             * doesn't support WPA2, these mode can be enabled by commenting below line */
	     .threshold.authmode = WIFI_AUTH_WPA2_PSK,
        },
    };
    ESP_ERROR_CHECK(esp_wifi_set_mode(WIFI_MODE_STA) );
    ESP_ERROR_CHECK(esp_wifi_set_config(WIFI_IF_STA, &wifi_config) );
    ESP_ERROR_CHECK(esp_wifi_set_ps(WIFI_PS_NONE)); // FMOD
    ESP_ERROR_CHECK(esp_wifi_start() );

    ESP_LOGI(TAG, "wifi_init_sta finished.");

    /* Waiting until either the connection is established (WIFI_CONNECTED_BIT) or connection failed for the maximum
     * number of re-tries (WIFI_FAIL_BIT). The bits are set by event_handler() (see above) */
    EventBits_t bits = xEventGroupWaitBits(s_wifi_event_group,
            WIFI_CONNECTED_BIT | WIFI_FAIL_BIT,
            pdFALSE,
            pdFALSE,
            portMAX_DELAY);

    /* xEventGroupWaitBits() returns the bits before the call returned, hence we can test which event actually
     * happened. */
    if (bits & WIFI_CONNECTED_BIT) {
        ESP_LOGI(TAG, "connected to ap SSID:%s password:%s",
                 EXAMPLE_ESP_WIFI_SSID, EXAMPLE_ESP_WIFI_PASS);
    } else if (bits & WIFI_FAIL_BIT) {
        ESP_LOGI(TAG, "Failed to connect to SSID:%s, password:%s",
                 EXAMPLE_ESP_WIFI_SSID, EXAMPLE_ESP_WIFI_PASS);
    } else {
        ESP_LOGE(TAG, "UNEXPECTED EVENT");
    }

    #if 0   // FMOD
    /* The event will not be processed after unregister */
    ESP_ERROR_CHECK(esp_event_handler_instance_unregister(IP_EVENT, IP_EVENT_STA_GOT_IP, instance_got_ip));
    ESP_ERROR_CHECK(esp_event_handler_instance_unregister(WIFI_EVENT, ESP_EVENT_ANY_ID, instance_any_id));
    vEventGroupDelete(s_wifi_event_group);
    #endif
}

void app_main(void)
{
    //Initialize NVS
    esp_err_t ret = nvs_flash_init();
    if (ret == ESP_ERR_NVS_NO_FREE_PAGES || ret == ESP_ERR_NVS_NEW_VERSION_FOUND) {
      ESP_ERROR_CHECK(nvs_flash_erase());
      ret = nvs_flash_init();
    }
    ESP_ERROR_CHECK(ret);

    ESP_LOGI(TAG, "ESP_WIFI_MODE_STA");
    wifi_init_sta();
}

If possible, attach a picture of your setup/wiring here.

No special setup, nothing is connected to the ESP32S3 devboard.

Code to reproduce this issue

Refer to example code

Other info: ESP32S3 log: 10_WiFi_Disconnect.txt Packet capture on CH9 (rename to .pcap): 10_WiFi_Disconnect.log Flash dump (rename to .bin): 10_WiFi_Disconnect.zip sdkconfig (remove file extension): sdkconfig.txt Router: Huawei E5885Ls-93a

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 50 (1 by maintainers)

Most upvoted comments

My boards looking like this, they have no “2022 v1.3” on it! IMG_20240228_175456

@Solar320 I knew your board is this, and I have purchased it and it’s on the way. I saw in one of your comments that you wanted to test the ESP32-S3 2022 v1.3 board, and I happen to have one, so I tested with it and the issue can’t be reproduced, then I share the test results with you.

My other purpose is to hope you to confirm whether my connection between the ESP and the breadboard is correct.

Ok then I missunderstood you. Your connection should be correct to supply the Board direct with 3,3V. You should be carefull when you also connect the USB the same time, it should not have an influence but you never know…

@sivar your link should be the right one.

I bought my board there: https://de.aliexpress.com/item/1005004639132852.html?spm=a2g0o.order_list.order_list_main.82.50cc5c5fSSVejr&gatewayAdapt=glo2deu

If the link do not work search for TZT-FIVE-STARS Store and Tzt ESP32-S3-DevKitC-1 ESP32-S3 wifi I hope this is working.

I get my module now, it look little different than on the product photo. And it has clearly another Antenna!

This module was connected to the right COM-USB-C and is working “without Pins”, with soldered Pins and also when it is connected to the breadboard. The Label is different, my old modules has the Label N16R8 and P2N8 the productphoto has only one label MON16R8 and the modul I get now, has also only one label N16R8

The Antenna is now super stable.

IMG_20240301_182437 IMG_20240301_165032 IMG_20240301_165055

IMG_20240301_165000

@zhangyanjiaoesp I have the exact same board as Solar320. I bought it on aliexpress: https://de.aliexpress.com/item/1005006266375800.html (N16R8 version)

@sivar2311 @Solar320 we will test locally and feedback ASAP.

@ble0 The issue is that the AP has not cleared the AUTH state of the previous connection.Hence The AP is not able to reply to the AUTH. In the connected capture,The STA sends a Deauth before sending an auth ,Which helps in clearing the state of the AP and hence the AP is able to respond to the AUTH req from STA. Sending Deauth before Auth was recently removed as it created other issues.We will provide a better workaround for this problem shortly.