It's an old issue, but an obvious need. Here's the closest thing I have found from espressif. But it does not support IoS. Is there more?
https://github.com/espressif/esp-iot-so ... th/ble_ota

I recently tested this on SPI lines to reduce EMI, it appears to work great on an ESP32-S3. Setting 0 might be too extreme depending on your clock rate. gpio_set_drive_capability((gpio_num_t)brd->GPIO_LCD_CLK, GPIO_DRIVE_CAP_0); gpio_set_drive_capability((gpio_num_t)brd->GPIO_LCD_DIN, GPIO_DRIVE_CAP...

True but documentation should replace the role if code. These are supposed to be examples for most platforms used by newcomers. This would be much better. #ifndef CONFIG_IDF_TARGET_ESP32S2 #error This example only supported on ESP32S2 #endif From what I can tell the S3's dedicated GPIO does not supp...

I see other topics that the matrix_keyboard example only works for devices with dedicated GPIO. But it seems to only have been tested with the S2, not the S3 which also has dedicated GPIO. Although the S3 does seem to lack this definition: SOC_DEDIC_GPIO_HAS_INTERRUPT Could this work on on an S3 wit...

Deleting both the c:\users\username\esp\esp-idf and c:\mos then restarting the installer again appears to have solved it.

I cannot use extension to install esp-idf 4.4.2 (release version) ModuleNotFoundError: No module named 'setuptools.command.build' The error message is difficult to understand, should I open an issue on https://github.com/espressif/vscode-esp-idf-extension/issues/new?assignees=&labels=bug-report&temp...

The lab is scheduled, but the test tool will not upload over serial. I can only assume it's because it changes the baud rate for upload from what is selected 115200 to 921600 which is more than my FTDI cable can support. Console: ESP_MAC: 00:00:00:00:00:00 Connecting........_____....._____....._____...

As I mentioned, it does not appear to work. Either I am misunderstanding this change, or it is not used when using the Arduino framework.

I also tried using:

I have a PCB where I need pullups on GPIO34-39, because I was not aware the software ones do not work. The documentation is very misleading, they should not be called GPIO at all, but I digress.. However, I also see this post that suggests you can workaround by using the RTC subsystem, but I was not...

@joeservo Sorry I did not see this.

By manual I meant pressing the button to pull GPIO0 low, rather then letting the RTS/DTR do it.

I found that the 100nF cap I had on GPIO causes problems, my board only works to automatically program with no cap.