When I read the first 4 bytes from app2 partition, I see 0xE9 0x05 0x02 0x22. How are you doing this? esptool.py? I trust the bootloader when it says there's actually 00 05 02 02 there. Have you erased that region of flash beforehand? Not doing this is likely to be your problem based on those seque...

Probably related (WiFi driver retrying many times): https://github.com/espressif/esp-idf/issues/9383

And that indicates that no changes are planned so you might consider exclusively using broadcasts instead, with your own acknowledgement implementation on top of that if necessary.

You can use esp_image_get_metadata(): https://github.com/espressif/esp-idf/bl ... #L115-L127

https://gist.github.com/boarchuz/1a40a6 ... b61388436f

Note the 'WDT_STAGE_ACTION_RESET_RTC'

gpio_config_t is not initialised

Also you config(21) and then set_level(11)

I'm not sure exactly which field controls the delay but if you mess with these one-by-one and view the result with your oscilloscope, you'll find it eventually: https://github.com/espressif/esp-idf/blob/master/components/soc/esp32s3/include/soc/i2c_reg.h Some likely candidates: I2C_SCL_LOW_PERIOD, I...

Setting compiler optimisation to 'Size', log level to 'None', and assertions to 'Silent' should get you most of the way there. Enabling nano formatting options also helps a lot iirc (uses printf in ROM so you don't need it linked in your binary). Also see: https://docs.espressif.com/projects/esp-idf...

Station config has fields to control how the driver should select the best AP:
https://github.com/espressif/esp-idf/bl ... #L386-L387
Or you can use custom logic and specify the BSSID.

Yes, this is documented behaviour affecting 36 and 39. Look up the ESP32 errata document for details. I wouldn't have expected it to trigger continuously though, only once on initialisation when the ADC is powered up. Are you using automatic light sleep, or manually disabling and enabling BLE period...