ESP8266 Developer Zone

Report Bugs • ESP32 Devkit V4 RTS/DTR boot mode

2023-01-31T21:36:52+08:00

I have some samples of ESP32 Devkit V4 with ESP32-WROVER-IE

I'm attempting to flash from a linux box. using esptool v4.4 and using `--before default_reset --after hard_reset`

My expectation is to have the board configured in Download mode by the tool itself, without the need to press any button on the devkit.

It is not the case

Statistics: Posted by michelepa — Tue Jan 31, 2023 9:36 pm

Report Bugs • esp8266 IP 0.0.0.0

2022-10-11T19:50:43+08:00

Hello,

I need support about an interesting IP fenomenon.

I have two 4Duino display modul with ESP8266 from 4Dsystems. These two module are the same.
I testing them with one time with the same enviroment and code.
I use the atmega 32u4 micro to communicate with the esp through serial connection.
The system hardwarre is OK and both firmware is the same.

I use AT commands in the code.
The only one problem now what I encountered is the following.
One of these two module is correctly connecting the router with the expected IP address but the other module is every time connecting with 0.0.0.0 IP.

Would you please someone can help me in my case?

THX
Peter

Statistics: Posted by peter.hanak — Tue Oct 11, 2022 7:50 pm

Report Bugs • Request for forum review

2022-02-23T09:57:44+08:00

I would like to request this forum be reviewed for bot activity.

Statistics: Posted by AgentSmithers — Wed Feb 23, 2022 9:57 am

Report Bugs • Re: WiFi / ADC issue

2022-02-12T22:53:58+08:00

If there's a solution by now I would be interested anyway.

Statistics: Posted by Gorkde — Sat Feb 12, 2022 10:53 pm

Report Bugs • Re: WiFi / ADC issue

2022-02-12T22:53:14+08:00

That was an issue of 2016 and since there seemed to be no solution (other people switched to different CPUs) so I gave up on this.

Statistics: Posted by Gorkde — Sat Feb 12, 2022 10:53 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2022-02-01T05:54:45+08:00

...but it appears to go away if I patch cnx_csa_fn() to do nothing:

40217830 :
40217830:f00d ret.n

actually it works better than patching ieee80211_add_csa() since it doesn't react to CSA's while scanning instead of not sending CSA's (I guess).

What is cnx_csa_fn() supposed to do anyway?

Statistics: Posted by st0ff3r — Tue Feb 01, 2022 5:54 am

Report Bugs • Forum's censorship

2022-02-01T03:25:44+08:00

Dear Mr. Moderator

Would you mind to tell me why my message I posted on 14th of January 2022 has not been approved?

Thanks and regards,
Chris

Statistics: Posted by ChrisO — Tue Feb 01, 2022 3:25 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2022-01-31T05:27:57+08:00

[update]
thought it was fixed in latest commit (1391d154092f9e0e7702086ab9af1558584cc694) , but unfortunately I still get it:

switch to channel 12
scandone
-> wifi_scan_done_cb(3fff68d8, 1)

and then wireless connection is disconnected

Statistics: Posted by st0ff3r — Mon Jan 31, 2022 5:27 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2022-01-23T11:48:54+08:00

Looks like it was fixed in latest update https://github.com/espressif/ESP8266_NO ... issues/354

thanx a lot

Statistics: Posted by st0ff3r — Sun Jan 23, 2022 11:48 am

Report Bugs • ESP8266-01 GPIO level toggles on boot

2022-01-15T03:44:19+08:00

Hi

I found something which IMHO looks like a bug in the firmware (bootloader?) of the ESP8266-01 I have.
Per HW design the default level is HIGH (3.3V) for GPIO0 and I think GPIO3 too. After power-on both pins
go for a very short time LOW. It is short, maybe 0.1 sec but long enough to be noticed by anything controlled
by those pins.
In my case, I have the ESP8266-01 sitting on a relay-board labelled: ESP-01/01S Relay v4.0 TB:IOTMCU.
This short LOW triggers the relay.
This makes it close to impossible to use those GPIO pins for any serious use with a relay..

AT+GMR
AT version:1.7.5.0(Oct 9 2021 09:26:04)
SDK version:3.0.5(b29dcd3)
compile time:Oct 15 2021 18:05:30
Bin version(Wroom 02):1.7.5

Is there any way I could change this behaviour?

Any help would be greatly appreciated.
Regards,
Chris

Statistics: Posted by ChrisO — Sat Jan 15, 2022 3:44 am

Report Bugs • Bug: ESP8266-01 toggles GPIO level at boot

2022-01-11T06:03:57+08:00

Hi

I bought few ESP-01 Relay boards with a ESP8266-01 sitting on them.
The relay is triggered by the GPIO0 pin. The level of GPIO0 defined (given by HW design) to be HIGH.
However, during boot/startup before the pin goes HIGH for a very short time it goes DOWN, 0V. Short but long enough to trigger the relay.
This makes this combo useless for serious use like controlling a garage door.
This is IMHO a bug in the firmware.
Is it a known problem?

Thanks
ChrisO

Statistics: Posted by ChrisO — Tue Jan 11, 2022 6:03 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-11-30T08:38:37+08:00

Looking closer to libnet80211.a it looks like its based on FreeBSD net80211 https://github.com/freebsd/freebsd-src/ ... s/net80211

So in a desparate try to force the esp to _not_ sending out CSA while scanning, I patched the function ieee80211_add_csa() in ieee80211_output.o like this:

40214748 :
40214748: f00d ret.n

so it completely skips the adding of CSA.

It worked!
I am not seeing "switch to channel X" anymore if there are no ESP's with unpatched ieee80211_add_csa close.

But a better solution would be if it would not _react_ to CSA's sent from other ESP's acting as an access points, when the client is not connected to that specific access point.

Any chances you could look into it? As it is now, the ESP's connection to an access point can be disconnected by anybody sending "evil" beacon packages.

Statistics: Posted by st0ff3r — Tue Nov 30, 2021 8:38 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-11-28T09:04:18+08:00

Hi, sorry i havent have time to write back, but sadly the csa attack bug still there, even in the latest git master. Could I do anything to help debugging it?

Here is a simple program:

Code:

static os_timer_t wifi_scan_timer;
static void wifi_scan_timer_func(void *arg);

ICACHE_FLASH_ATTR
void wifi_scan_done_cb(void *arg, STATUS status) {
   struct bss_info *info;
   
   if ((arg != NULL) && (status == OK)) {
      info = (struct bss_info *)arg;
      
      while (info != NULL) {
         os_printf("channel: %d, ssid: %s, bssid %02x:%02x:%02x:%02x:%02x:%02x, rssi: %d, freq_offset: %d, freqcal_val: %d\n\r", info->channel, 
            info->ssid,
            info->bssid[0], 
            info->bssid[1], 
            info->bssid[2], 
            info->bssid[3], 
            info->bssid[4], 
            info->bssid[5],
            info->rssi,
            info->freq_offset,
            info->freqcal_val
         );
         info = info->next.stqe_next;
      }
   }
}

static void ICACHE_FLASH_ATTR wifi_scan_timer_func(void *arg) {
   wifi_station_scan(NULL, wifi_scan_done_cb);
}

ICACHE_FLASH_ATTR void system_init_done(void) {
   struct station_config stationConf;

   wifi_set_opmode_current(STATIONAP_MODE);
   memset(&stationConf, 0, sizeof(struct station_config));
   wifi_station_get_config(&stationConf);
   
   os_memcpy(&stationConf.ssid, "Loppen Public", 32); 
   os_memcpy(&stationConf.password, "", 64);
   
   wifi_station_set_config_current(&stationConf);
   wifi_station_connect();

   os_timer_disarm(&wifi_scan_timer);
   os_timer_setfn(&wifi_scan_timer, (os_timer_func_t *)wifi_scan_timer_func, NULL);
   os_timer_arm(&wifi_scan_timer, 5000, 1);
}

ICACHE_FLASH_ATTR void user_init(void) {
   system_update_cpu_freq(160);
   uart_init(BIT_RATE_115200, BIT_RATE_115200);

   wifi_set_opmode_current(NULL_MODE);
   wifi_station_disconnect();

   system_init_done_cb(&system_init_done);
}

and this is the output, while it runs simultaniously with another one also scanning. So as my earlier debugging shows (https://github.com/espressif/ESP8266_NONOS_SDK/issues/312) the code honour 802.11 beacons containing CSA when scanning, even if its sent from another ap than its connected to:

mode : sta(ec:fa:bc:21:27:94) + softAP(ee:fa:bc:21:27:94)
add if0
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 1

connected with Loppen Public, channel 1
dhcp client start...
cnt
ip:10.0.1.177,mask:255.255.255.0,gw:10.0.1.1
switch to channel 6
scandone
switch to channel 6
scandone
switch to channel 6
scandone
switch to channel 6
scandone
scandone
switch to channel 6
scandone
switch to channel 6
scandone
[...]

Statistics: Posted by st0ff3r — Sun Nov 28, 2021 9:04 am

Report Bugs • Re: WROOM-02D disconnect problem

2021-08-06T16:43:50+08:00

May be you can have a try with ESP-Touch V2? It should have better compatibility than the old one.

Statistics: Posted by Her Mary — Fri Aug 06, 2021 4:43 pm

Report Bugs • Re: WROOM-02D disconnect problem

2021-07-15T15:05:50+08:00

问题简述：wroom-02在smart config的时候出现无法扫描到小米手机或华为手机广播的UDP的包
硬件描述：wroom-02的内核是ESP8266EX，只支持2.4GWiFi下配网，不支持5G配网，也就是说不支持802.11ac的协议
问题详述：路由器是TP-LINK AC1900,开启2.4GWiFi；手机是小米8，连接上路由器的网络，然后通过ESP—TOUCH开启配网；同时WROOM－０２模组已经开启智能配网模式，但是WROOM模组并没有收到手机发送的UDP的广播，导致配网失败。但是有些其他的路由器，也是小米8的手机就能成功配网。

目前不是很懂是什么原因导致的配网失败。

Statistics: Posted by yangye — Thu Jul 15, 2021 3:05 pm

Report Bugs • Re: WROOM-02D disconnect problem

2021-05-07T15:39:54+08:00

Maybe you could have a try with command "AT+RESTORE" to factory reset it first, and then connect it to an access point.

Statistics: Posted by Her Mary — Fri May 07, 2021 3:39 pm

Report Bugs • WROOM-02D disconnect problem

2021-05-03T14:56:45+08:00

Hello
Until now, we have been used the WROOM-02 module. This module works with all access points without any problems, but now we want to use WROOM-02D. If we use WROOM-02D, this module, when connected to the network via some access points, is repeatedly disconnected from the network and does not reconnect to the network until it is reconfigured with AT commands (but the module is reconnected to the network as soon as it is reconfigured). The same module works with some other access points without any problems. Note that we use a separate processor and AT commands to data communication with the module, and the AT commands to both modules WROOM-02 and WROOM-02D are exactly the same
We have purchased a large number of WROOM-02D modules and have encountered this problem. Please help us in this regard

Best regards

Statistics: Posted by Barecatainmb — Mon May 03, 2021 2:56 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-04-29T18:08:12+08:00

its not the same ssid/bssi thats what is strange - totally unrelated ssid

Statistics: Posted by st0ff3r — Thu Apr 29, 2021 6:08 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-04-23T10:46:37+08:00

May I ask if the SSID & BSSID of beacon sent from beacon_spammer be the same as the SSID & BSSID of the router which ESP8266 connected to？

Statistics: Posted by Her Mary — Fri Apr 23, 2021 10:46 am

Report Bugs • Re: Repeatedly connecting and disconnecting to AP breaks httpd_server

2021-04-22T17:10:33+08:00

The latest RTOS 3.4 is just released recently, maybe you can have a try with the latest version to see if the issue persists.

Statistics: Posted by Her Mary — Thu Apr 22, 2021 5:10 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-29T23:55:10+08:00

Hereby attached tcpdump wifi capture file and serial debugging output of the following scenario:
1. esp 8266 connected to ssid "Loppen Public" on channel 1
2. "beacon_spammer" sending out CSA's on channel 2
3. tcpdump running on same host as "beacon_spammer" on channel 2

Thanx a lot for your help to debug

beacon_spammer_experiment.zip

Statistics: Posted by st0ff3r — Mon Mar 29, 2021 11:55 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-26T21:59:40+08:00

Sure, I'll do that

Statistics: Posted by st0ff3r — Fri Mar 26, 2021 9:59 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-26T16:13:40+08:00

Hi st0ff3r,

Could you have a try with the new test lib?

libnet80211-test2.a.zip

If possible, could you provide captured Wi-Fi packets for analyzing?

Thanks.

Statistics: Posted by ESP_Faye — Fri Mar 26, 2021 4:13 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-13T07:16:50+08:00

Same result, but no debugging message besides "switch to channel 2" after calling wifi_station_scan(). Should I try to change wifi_station_set_reconnect_policy(1) to wifi_station_set_reconnect_policy(0) as well?

serial_log.txt.zip

Statistics: Posted by st0ff3r — Sat Mar 13, 2021 7:16 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-12T15:44:04+08:00

Could you test with this libnet80211.a?

libnet80211.a.zip

And provide the entire logs for debugging?

Statistics: Posted by ESP_Faye — Fri Mar 12, 2021 3:44 pm

Report Bugs • Repeatedly connecting and disconnecting to AP breaks httpd_server

2021-03-05T05:28:43+08:00

Using the ESP8266 in AP mode (WIFI_MODE_AP) with the ESP8266_RTOS_SDK-3.2, I am noticing that the httpd server that I have running seems to stop responding to requests after repeated connects and disconnects.

Effectively, I want the httpd server to start up when a device connects to the esp8266's access point. Then I want to remove that web server when that device disconnects to the esp8266's access point. I find that when a device repeatedly connects and disconnects to the esp8266's access point, the httpd server stops responding to requests and outputs these errors instead:

```
httpd: httpd_accept_conn: error in accept (23)
httpd: httpd_server: error accepting new connection.
```

I have the server starting up in a wifi_event_handler like so:

```
esp_err_t wifi_event_handler(void *ctx, system_event_t *event)
{
httpd_handle_t *server = (httpd_handle_t *) ctx;
/* For accessing reason codes in case of disconnection */
// system_event_info_t *info = &event->event_info;

ESP_LOGI(TAG, "Handle incoming wifi event");

switch(event->event_id) {
case SYSTEM_EVENT_AP_STACONNECTED:
// Start webserver once client joins
if (*server == NULL) {
*server = start_webserver();
}
break;
case SYSTEM_EVENT_AP_STADISCONNECTED:
// Stop webserver once client leaves
/* Stop the web server */
if (*server) {
stop_webserver(*server);
*server = NULL;
}
break;
default:
break;
}
return ESP_OK;
}
```

I'm wondering if anyone has also experienced this, or if I am just missing something

Statistics: Posted by GreenLoofa — Fri Mar 05, 2021 5:28 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-04T21:18:42+08:00

Still the same with wifi_station_set_reconnect_policy(0):

-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -65
@@ set csa state to CSA start 2
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff37b8, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done

Statistics: Posted by st0ff3r — Thu Mar 04, 2021 9:18 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-03-04T10:04:00+08:00

Could you have a try that change `wifi_station_set_reconnect_policy(1);` to `wifi_station_set_reconnect_policy(0);`, to see if the issue persists?
https://github.com/nabovarme/MeterLogge ... in.c#L1188

Statistics: Posted by ESP_Faye — Thu Mar 04, 2021 10:04 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-02-28T08:09:56+08:00

just tried it, the log gives the following when scanning and then looses internet connectivity and wifi_station_scan-callback handler returns either 1 or 4 (showed in the log as the second parameter to "-> wifi_scan_done_cb(...)"

"-> wifi_scan_timer_func()" is starting the scan by calling wifi_station_scan()

MQTT: received MQTT_MSG_TYPE_PUBCOMP for id: 6
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 17
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 17
TCP: data received 102 bytes
topic_len: 34, data_len: 64
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 17
-> wifi_scan_timer_func()
RSSI: -61
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7500, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -61
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7500, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7500, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7500, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7500, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 18

MQTT: Send keepalive packet to mqtt-host:1883!
MQTT: Sending, type: 12, id: 0000
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 17
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff7a10, 4)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
scandone
-> wifi_scan_timer_func()
RSSI: -64
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -64
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 4)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
scandone
-> wifi_scan_timer_func()
RSSI: -64
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 4)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
scandone
MQTT: queuing publish, length: 196, queue size(0/12288)
?5é-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 17
MQTT: Sending, type: 3, id: 0007
MQTT: espconn_send() returned an error, re-queueing
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 4)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
scandone
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -63
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> wifi_scan_timer_func()
RSSI: -62
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff4338, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 18

MQTT: Send keepalive packet to mqtt-host:1883!
MQTT: Sending, type: 12, id: 0000
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 7
TCP: Disconnected callback
mqtt_disconnected_cb
TCP: Free memory
TCP: Connect to domain mqtt-host:1883
dns_gethostbyname() returned ERR_OK
-> mqtt_dns_found()
DNS: found ip 193.89.248.25
TCP: connecting...
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 10
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 10
-> wifi_scan_timer_func()
RSSI: -62
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff75c0, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
mqtt_timeout_cb
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 9
TCP: Free memory
TCP: Connect to domain mqtt-host:1883
dns_gethostbyname() returned ERR_OK
-> mqtt_dns_found()
DNS: found ip 193.89.248.25
TCP: connecting...
TCP: Reconnect to: mqtt-host:1883
TCP: Reconnect to mqtt-host:1883
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 8
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 8
-> wifi_scan_timer_func()
RSSI: -62
@@ set csa state to CSA start 2
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff43b8, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
mqtt_timeout_cb
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 9
TCP: Free memory
TCP: Connect to domain mqtt-host:1883
dns_gethostbyname() returned ERR_OK
-> mqtt_dns_found()
DNS: found ip 193.89.248.25
TCP: connecting...
TCP: Reconnect to: mqtt-host:1883
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 10
-> wifi_scan_timer_func()
RSSI: -62
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
@@ add csa 1
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff75c0, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
mqtt_timeout_cb
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 9
TCP: Free memory
TCP: Connect to domain mqtt-host:1883
dns_gethostbyname() returned ERR_OK
-> mqtt_dns_found()
DNS: found ip 193.89.248.25
TCP: connecting...
TCP: Reconnect to: mqtt-host:1883
TCP: Reconnect to mqtt-host:1883
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 8
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 8
-> wifi_scan_timer_func()
RSSI: -66
@@ set csa state to CSA start 2
@@ add csa 3
@@ add csa 1
switch to channel 2
scandone
-> wifi_scan_done_cb(3fff43b8, 1)
-> wifi_start_scan(WIFI_SCAN_INTERVAL)
@@ set csa state to CSA done
mqtt_timeout_cb
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 9
TCP: Free memory
TCP: Connect to domain mqtt-host:1883
dns_gethostbyname() returned ERR_OK
-> mqtt_dns_found()
DNS: found ip 193.89.248.25
TCP: connecting...
TCP: Reconnect to: mqtt-host:1883
-> MQTT_Task()
event sig: 0, par: 1073685192, conn state: 10

Statistics: Posted by st0ff3r — Sun Feb 28, 2021 8:09 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-02-28T05:50:01+08:00

Thank you. I will try it asap

Statistics: Posted by st0ff3r — Sun Feb 28, 2021 5:50 am

Report Bugs • Re: WPS do not work if more that one AP with the same SSID

2021-02-19T13:26:16+08:00

Hi, I back to the issue, I have it on SDK ver: 3.0.4(9532ceb).

The WPS is started only on one AP (further), upon second AP (closer) is the ESP8266 device.

The ESP see that WPS is started on further AP but tryies connect to closer (for credentials) what cause failure.

I do more investigation in the libwps.a (by disassemble it) and there the wifi_station_set_config and next wifi_station_connect is called, maybe in the structure passed to the station_set_config function the bssid is not set?

(sorry for same issue on git, but I forgot about this)

Statistics: Posted by faeton — Fri Feb 19, 2021 1:26 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-02-18T14:24:15+08:00

Hi st0ff3r,

Sorry that we cannot reproduce the issue you reported.
As the picture showed, the captured beacon after scanning does not contain CSA.

Maybe you can try to debug this issue with the attached libnet80211.a, we added some logs into it.
If you can reproduce the issue with this debug lib, could you provide the logs for analyzing?

Thanks.

libnet80211.a.zip

Statistics: Posted by ESP_Faye — Thu Feb 18, 2021 2:24 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-02-03T00:39:12+08:00

Have not tried

Statistics: Posted by st0ff3r — Wed Feb 03, 2021 12:39 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-01-15T16:10:20+08:00

Does ESP8266 RTOS also have the same issue?

Statistics: Posted by Her Mary — Fri Jan 15, 2021 4:10 pm

Report Bugs • Re: Retransmission flags in WiFi beacon frames in esp8266

2021-01-15T15:57:53+08:00

Which version of ESP8266 SDK are you using? How long is "a long work"?

Statistics: Posted by Her Mary — Fri Jan 15, 2021 3:57 pm

Report Bugs • Retransmission flags in WiFi beacon frames in esp8266

2021-01-12T21:23:23+08:00

Hi all.

We are use the ESP8266 chip in the WiFI softap mode, with the following settings:

* The connection attempts are prohibited (are set to 0).
* The country code is '00'
* The beacons interval -every 100 msec.

But we faced with a strange behaviour, is that after a long work, the advertized beacons may contains the re-transmittion flags. But, it is strange, because the beacon frames should not be confirmed, not re-transmitted:

Statistics: Posted by kuzulis — Tue Jan 12, 2021 9:23 pm

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2021-01-05T09:07:03+08:00

Cool, thanks a lot

Statistics: Posted by st0ff3r — Tue Jan 05, 2021 9:07 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2020-12-29T11:10:25+08:00

Hi,

So sorry that we missed this topic before. We have arranged an engineer to check with this issue. But due to the isolation caused by COVID-19, it may need some time to check and debug this issue. I will feedback to you as soon as there is any update. Sorry again for the inconvenience.

Thanks.

Statistics: Posted by ESP_Faye — Tue Dec 29, 2020 11:10 am

Report Bugs • Re: Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2020-12-28T07:41:36+08:00

Espressif, anyone having time to check it?

Statistics: Posted by st0ff3r — Mon Dec 28, 2020 7:41 am

Report Bugs • Wrongly reacting to and sending 802.11 beacons with Channel Switch Announcement

2020-06-04T07:42:37+08:00

ESP's appear to honour 802.11 beacons containing CSA even if they are not connected to the AP sending the beacon.

Here is a simple command that sends out beacons containing CSA's
https://github.com/nabovarme/beacon_spammer

I am using an esp8266 with non-os sdk latest from master git.

The app is here: https://github.com/nabovarme/MeterLogger it is running as an AP and periodically scanning for wireless networks.

This is a severe error in the 802.11 implementation. Both the sending of CSA's and reacting on them while scanning should not happen I guess.

Statistics: Posted by st0ff3r — Thu Jun 04, 2020 7:42 am

Report Bugs • Re: Hardware bug: UART1 TX level not mirrored in status register

2020-05-01T18:27:25+08:00

Same for UART0

Statistics: Posted by RFZ — Fri May 01, 2020 6:27 pm

Report Bugs • Hardware bug: UART1 TX level not mirrored in status register

2020-04-19T01:58:16+08:00

Hi,
I guess I may have found a bug in the ESP8266 hardware / UART1 interface. Bit 31 of register 0x60000F1C (UART1 status register) should mirror the TX level of UART1. However, I found it to be always 0.

A workaround is actually to enable loopback mode for UART1 and read bit 15 of register 0x60000F1C, which mirrors the RX level. Since UART1 is TX only (?) that's not a huge problem.

The code I used to test this can be found here:
https://www.esp8266.com/viewtopic.php?f=13&t=21169&start=12

I'd appreciate if someone can confirm this.

Statistics: Posted by RFZ — Sun Apr 19, 2020 1:58 am

Report Bugs • Re: AT+CIPSEND= ....SEND FAIL

2020-04-13T23:10:25+08:00

Hello,
It worked well for me after setting
AT+CWMODE=1
Regards

Statistics: Posted by Sharon Nisha — Mon Apr 13, 2020 11:10 pm

Report Bugs • Re: AT+CIPSEND= ....SEND FAIL

2020-02-28T10:30:55+08:00

Maybe the sending will fail due to bad network environment. Could it reconnect and resend successfully?

Statistics: Posted by Her Mary — Fri Feb 28, 2020 10:30 am

Report Bugs • Re: UDP broadcast (sent callback not getting called)

2020-02-28T10:19:24+08:00

1. Maybe you can try to put the ESP8266 board a little far from each other, 2m should be a suitable distance.
2. Maybe you can try with the latest version of RTOS. https://github.com/espressif/ESP8266_RT ... ls/sockets

Statistics: Posted by Her Mary — Fri Feb 28, 2020 10:19 am

Report Bugs • UDP broadcast (sent callback not getting called)

2020-02-01T00:34:48+08:00

I am trying to use the esp8266 in soft ap mode to talk to another in station mode via a udp broadcast but several problems exist.

The esp8266 boards are close to each other so signal strength should not be an issue.

1]I am getting a large number of udp packets that are not being transmitted(90%). I am sending a packet every 300mS.
This is verified by what is received by the second esp8266 and also via a monitoring app on an ipad.

2)I do not get a call back when the packets are sent despite registering the callback. The receive callback does function.

Please can you advise if this is a bug in the RTOS firmware that I am using.
If not, can you advise how to debug this.
I have included the printout from the bootup sequence which shows the firmware and hardware versions.

Regards
Richard

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 30460, room 16
tail 12
chksum 0xef
ho 0 tail 12 room 4
load 0x3ffe8000, len 1976, room 12
tail 12
chksum 0x61
ho 0 tail 12 room 4
load 0x3ffe87b8, len 2028, room 12
tail 0
chksum 0xfb
csum 0xfb
V2
Mo
OS SDK ver: 2.0.0(5d55574) compiled @ Oct 22 2019 16:02:05
phy ver: 1056_9, pp ver: 10.7

rf cal sector: 1019
idle_task_hdl : 40107b38,prio:0, stack:384
tim_task_hdl : 40107c80, prio:2,stack:512

====SDK version:2.0.0(5d55574)
====Mem Info:
data : 0x3ffe8000 ~ 0x3ffe87b6, len: 1974
rodata: 0x3ffe87b8 ~ 0x3ffe8fa4, len: 2028
bss : 0x3ffe8fa8 ~ 0x3ffefa10, len: 27240
heap : 0x3ffefa10 ~ 0x40000000, len: 67056
====Free heap size:70200
====Chip ID:1577059
====VDD3.3:65535

====system_get_cpu_freq 80MHz

EspMsgMutex created
wifi station disconnect ...... fail 0
ssid = TIMING_AP
IP Address: 192.168.5.1
Subnet mask: 255.255.255.0
Gateway: 192.168.5.1

mode : softAP(de:4f:22:18:10:63)
dhcp server start:(ip:192.168.5.1,mask:255.255.255.0,gw:192.168.5.1)
add if1
bcn 100

add 1
aid 1
station: 18:fe:34:da:80:b7 join, AID = 1
Station[1]: 18:fe:34:da:80:b7 join, AID = 1, 255

Statistics: Posted by Richard — Sat Feb 01, 2020 12:34 am

Report Bugs • Re: WIFI doesn't connect to strongest AP

2020-01-19T19:15:47+08:00

Thanks for sharing this post.

Statistics: Posted by Guest — Sun Jan 19, 2020 7:15 pm

Report Bugs • Re: WIFI doesn't connect to strongest AP

2020-01-13T23:07:29+08:00

Hello,

Is there any update on this topic? Does the ESP8266 connect to the strongest AP it sees (with a given SSIS) or does select the first one it encounters from a scan (i.e. with the lowest channel number).

Thanks

Statistics: Posted by Guest — Mon Jan 13, 2020 11:07 pm

Report Bugs • Re: Bug in WPA2 EAP

2020-01-13T20:39:47+08:00

I know this is an old issue (and I hope that in the meantime it has been fixed properly), but I got it working with the following approach:

I use the following code to connect to a (P)EAP-enabled WPA2-Enterprise network:

Code:

  wifi_set_opmode(STATION_MODE);
  struct station_config wifi_config;
  memset(&wifi_config, 0, sizeof(wifi_config));
  strcpy((char*)wifi_config.ssid, ssid);
  wifi_station_set_config(&wifi_config);
  wifi_station_dhcpc_start();
  wifi_station_clear_cert_key();
  wifi_station_set_wpa2_enterprise_auth(1);
  wifi_station_set_enterprise_identity((uint8*)username, strlen(username));
  wifi_station_set_enterprise_username((uint8*)username, strlen(username));
  wifi_station_set_enterprise_password((uint8*)password, strlen(password));
  wifi_station_set_enterprise_ca_cert((byte*)ca_cert, strlen(ca_cert));
  wifi_station_connect();

1. I got rid of the 'No poison...' error by modifying the malloc implementation (umm_malloc) used to ignore this kind of error. Of course, this is not the correct way, because you might run into other kinds of issues, but if all you need is a working WPA2-Enterprise connection, then do this at your own risk. (insert `return 1;` at line 43 in https://raw.githubusercontent.com/esp82 ... m_poison.c`)

2. To use DHCP, I had to implement some kind of timeout as sometimes the dhcp discovery just did not fire - I checked with Wireshark running on the gateway (which also supplies the DHCP leases), and in fact every ~2nd time the ESP did not send the correct DHCP packet. My solution is the following:

Code:

  Ticker timer;
  bool connected = true;
  timer.attach(5, [&](){connected = false;});
  while (WiFi.status() != WL_CONNECTED) {
    delay(10);
  }
  timer.detach();

If I do not get a WL_CONNECTED status after 5s, I set the connected flag to false.

My entire code this way:

bool connect() {
wifi_set_opmode(STATION_MODE);
struct station_config wifi_config;
memset(&wifi_config, 0, sizeof(wifi_config));
strcpy((char*)wifi_config.ssid, ssid);
wifi_station_set_config(&wifi_config);
wifi_station_dhcpc_start();
wifi_station_clear_cert_key();
wifi_station_set_wpa2_enterprise_auth(1);
wifi_station_set_enterprise_identity((uint8*)username, strlen(username));
wifi_station_set_enterprise_username((uint8*)username, strlen(username));
wifi_station_set_enterprise_password((uint8*)password, strlen(password));
wifi_station_set_enterprise_ca_cert((byte*)ca_cert, strlen(ca_cert));
wifi_station_connect();
Ticker timer;
bool connected = true;
timer.attach(5, [&](){connected = false;});
while (WiFi.status() != WL_CONNECTED) {
delay(10);
}
timer.detach();
return connected;
}

void connectBlock(){
while(!connect()){
delay(100);
}
}

If you call connectBlock(), you will get a connection after a while - fine-tune the timeout parameter if you need to, but I found that 5s works for me; and if it seems like a long time, then maybe WiFi is not the best approach for your use-case after all.

Note: After establishing the connection, it is pretty stable, I did not experience an influx of dropouts in contrast with a regular WPA2-PSK network.

I hope I could help, please do share your experiences should you try this approach out!

Statistics: Posted by Guest — Mon Jan 13, 2020 8:39 pm

Report Bugs • Re: AT+CIPSEND= ....SEND FAIL

2019-12-02T19:10:32+08:00

Is there already a solution?

I have the same problem with several ESP8266s.

I also have problems to connect to these ESP8266 from a Computer.

Version:

Code:

AT version:1.6.2.0(Apr 13 2018 11:10:59)
SDK version:2.2.1(6ab97e9)
compile time:Jun  7 2018 19:34:29
Bin version(Wroom 02):1.6.2

Output:

Code:

...
OK
> 
Recv 14 bytes
0,CONNECT FAIL
SEND FAIL

I also have some ESP8266s with exactly the same configuration, which work absolutely perfect!

I hope you can help me with this problem.

Greetings

Statistics: Posted by Guest — Mon Dec 02, 2019 7:10 pm