For one of my projects, I did this exact thing however, this was right during the shift to cmake so I did it in the old Makefile system; like so (where I created the esp-idf as a submodule in the idf directory): export IDF_PATH = $(PWD)/idf PROJECT_NAME := my_project include $(IDF_PATH)/make/project...

Something thats also strange is that if I set the channel parameter and run through all 11 channels by calling esp_wifi_scan_start 11 times, it works as expected; taking only about 540ms in the log (no longer than 600ms) to complete and this is with print statements between each scan (I also setup t...

Have you enabled Power Management? The DFS might be the cause of the issue as your i2c_master_read_slave doesnt include pm locks. Hi, Thanks for your reply! I have tried your suggestion, both using pm locks and disabled DFS in menuconfig: The clock looks better now but it still behaves strange and ...

Have you enabled Power Management? The DFS might be the cause of the issue as your i2c_master_read_slave doesnt include pm locks.

Hi mrrosen! I know it's been a long time but I was wondering if you were able to do the ADV_TYPE_DIRECT_IND_HIGH connection with your phone. If you have some code example or a source, where I can find some useful information, would be really helpful. Let me know if you know something!:) No luck yet...

Hi, Can you provide the IDF commit ID which version works fine and which version works incorrectly? thanks !! If you are referring to my issue with the TI BQ27621, I checked out the v3.1.1 tag and it didnt work, while checking out the v2.0 tag worked fine. However, since I was able to narrow down t...

May not be relevant to all of the I2C issues people are seeing, but with respect to occasional (or constant) timeout errors from i2c_master_cmd_begin , there is a change from IDF v2.x to v3.x that caused problems for me talking to a TI BQ27621 battery monitor. Changes in the I2C driver force the bit...

Sorry for any misunderstanding, but I do need an active scan to save time and am not sure if its possible to manually send probe requests while in promiscuous mode (though maybe, Im not sure). Still, I rather clear up the overhead from the builtin scan functions if possible before attempting that.

Im working on ESP32 with the ESP IDF; this appears to be code for ESP8266 Arduino.

While thats a thought, its not practical in our case. Im more wondering why ESP32 is taking 200%-300% the time of the scan (should be ~440ms @ 11ch,40ms/ch, but is taking ~2000ms with connection to complete; I can understand some overhead but this much?) before coming back with a scan complete messa...