CHIP:ESP32S3FH4R2
IDF VER: V4.4.4
issue:
I (697873) wifi:state: init -> auth (b0)
I (698874) wifi:state: auth -> init (200)
I (698874) wifi<11,0>, old:<11,2>, ap:<255,255>, sta:<11,2>, prof:1
Authorization timeout,I am sure the configuration is correct,
I grab the pk for use omnipeek,Found that no pk was sent out
so,I tested Micpython firmware WIFI.The result is the same.
I changed a board, the fault is the same
Attachment:sdkconfig
Who should I doubt now
wifi:state: auth -> init (200) ISSUE
Re: wifi:state: auth -> init (200) ISSUE
I'm experiencing the same. One out of three boards produces this behaviour.
ESP-IDF: v5.0
The boards in question are all Adafruit Feathers: https://www.adafruit.com/product/5438, there is nothing connected to the boards.
All chips identify themselves as:
I (374) quad_psram: This chip is ESP32-PICO-V3-02
ESP-IDF: v5.0
The boards in question are all Adafruit Feathers: https://www.adafruit.com/product/5438, there is nothing connected to the boards.
All chips identify themselves as:
I (374) quad_psram: This chip is ESP32-PICO-V3-02
Re: wifi:state: auth -> init (200) ISSUE
I am experiencing the same issue with ESP-WROOM-32. I get multiple failures to connect and after the retry counter overflows I get this:
assert failed: spinlock_acquire spinlock.h:122 (lock->count == 0)
Backtrace: 0x40081bfa:0x3ffbd7a0 0x4008a909:0x3ffbd7c0 0x40091999:0x3ffbd7e0 0x4008d4e6:0x3ffbd900 0x4008dd7d:0x3ffbd930 0x400d82df:0x3ffbd950 0x40171129:0x3ffbd970 0x40170c62:0x3ffbd9a0 0x40170d39:0x3ffbd9e0 0x4008d31d:0x3ffbda00
soon after the ESP reboots by itself and connects successfully. I don't want that behavior the best would be to connect on first try. Does anyone have any solution to this?
assert failed: spinlock_acquire spinlock.h:122 (lock->count == 0)
Backtrace: 0x40081bfa:0x3ffbd7a0 0x4008a909:0x3ffbd7c0 0x40091999:0x3ffbd7e0 0x4008d4e6:0x3ffbd900 0x4008dd7d:0x3ffbd930 0x400d82df:0x3ffbd950 0x40171129:0x3ffbd970 0x40170c62:0x3ffbd9a0 0x40170d39:0x3ffbd9e0 0x4008d31d:0x3ffbda00
soon after the ESP reboots by itself and connects successfully. I don't want that behavior the best would be to connect on first try. Does anyone have any solution to this?
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 95 guests