Hello. The wifi subsystem can store its settings in nvs. In my case I'm switching between AP and STA and APSTA modes during a scanning process, due to the limitations of the SoftAP. What I'm wondering is how to prove that I'm not wearing out the nvs. I'm pretty sure I'm not, and I could instrument m...

I'm having similar issues here with a v3.0-rc1 esp-idf based project. It shows up when hammering the libesphttpd server with the 'ab' utility but isn't always in the same location. I'm convinced its in my code but I'm having a really tough time tracking it down. How did you enable the per-allocation...

I'm starting to bump into flash size limits here with about .8MB of application. Much of that is system libraries, newlib, mbedtls, wifi libraries etc. I came across the ALB32-WROVER, https://www.analoglamb.com/product/alb32-wrover-esp32-module-with-64mb-flash-and-32mb-psram/, does anyone have exper...

I'm also interested in an update. I have both a NTC thermistor and an analog thermistor. I'm afraid to use the internal ADC going forward but would prefer to use the internal ADC vs. adding a $1+ ADC to the board.

Hello. Does anyone have an example of udp with the loopback interface? I have a server process waiting on a select() and would like to add the udp listener to its list of FDs so I can wake it up and shut it down cleanly from another thread. Using the loopback address was intended to avoid allowing o...

From debugging it looks like the udp_bind() in _mdns_server_init_api() is failing and returning ESP_ERR_INVALID_STATE. I'm running the radio in APSTA mode.

Starting mDNS on TCPIP_ADAPTER_IF_STA works find btw.

I've looked in esp32/include/rom/efuse.h, soc/esp32/include/soc/efuse_reg.h and bootloader_support/src/efuse.c and it isn't immediately obvious how one can determine if an efuse has been burnt. Is the developer supposed to first check whether the efuse has been read/write protected and then if not e...

Bump.

Apparently I should have added '--no-protect-key' at the end of the command! Would be great if that option was documented in the espefuse.py help but I should have read the wiki page more carefully in any case.

I'm going to swap the module out for another one and see how that option works.

I had posted a while ago about a unique id on the ESP32 for use in authenticating commands. Using espefuse.py I burnt a key to BLK3 like: $IDF_PATH/components/esptool_py/esptool/espefuse.py --port /dev/ttyUSB0 burn_key BLK3 blk3_key.bin Note that I used 'burn_key' because it seemed like the best app...