wifi bcn timeout error

[devang.dixit]

I (66037) wifi: bcn_timout,ap_probe_send_start
W (66037) wifi: alloc eb len=76 type=2 fail, heap:148


Why is this error occurring? How to resolve this?

[ESP_Sprite]

My guess is that you're out of memory (seems a heap alloc fails).

[devang.dixit]

wifi: bcn_timout,ap_probe_send_start
I (42295) wifi: ap_probe_send over, resett wifi status to disassoc
I (42295) wifi: state: run -> init (1)
I (42295) wifi: pm stop, total sleep time: 24918952 us / 36287703 us
I (42305) wifi: n:11 0, o:11 0, ap:255 255, sta:11 0, prof:1


can you please make me understand why this error is occurring?

[ESP_Sprite]

Looks to me like the WiFi AP you're connected to went down or out of range. The ESP32 didn't hear from it for a while, so it starts actively asking if the AP is still there. After it still does not get a response, it disassociates.

[devang.dixit]

No, I don't think this is the issue.
As my esp device and Ap are very near to each other(as the distance between the two is 4 feets).

[devang.dixit]

Task watchdog got triggered. The following tasks did not reset the watchdog in time:
- IDLE (CPU 1)
Tasks currently running:
CPU 0: IDLE
CPU 1: ipc1
I (32295) wifi: bcn_timout,ap_probe_send_start
I (34795) wifi: ap_probe_send over, resett wifi status to disassoc
I (34795) wifi: state: run -> init (1)
I (34795) wifi: pm stop, total sleep time: 18731090 us / 28985793 us

I (34805) wifi: n:11 0, o:11 0, ap:255 255, sta:11 0, prof:1


Sometimes I am getting these both error simultaneously.

[ESP_Sprite]

Are you perhaps doing large writes to flash?

[devang.dixit]

yes, but how to resolve this ?

[devang.dixit]

So, according to you, I should not do large write into flash. Wright?
Is there any other way to resolve this?
Currently I am usign esp-idf-v3.1-beta1.

[ESP_Sprite]

The issue is that most of the ESP32 is 'locked up' while doing flash writes; the architecture is somewhat dependent on being able to read code from the flash chip on the fly, and while doing a write it cannot do this, so it will suspend most tasks until the write is over. If you do a lot of large writes back-to-back, this means a bunch of tasks won't run for a long time, and the task watchdog kicks in. Suggest doing a vTaskDelay(10) or something between flash writes, to give other tasks the chance to run.