Generally, the Espressif devkit-C series are widely available and generally kept up-to-date with the latest SoC. Do note that we generally do not recommend using devkits as final products, as the composition of devkits isn't as stable as e.g. a module or chip. (As in: we won't change things in modul...

No, sorry, there's no way to do that. You could possibly get a few pins that run at 1.8V by doing some hackery with the pins in the Vcc_sio domain (but note that means moving the flash to custom pins, which you can only do using external flash), but that's way less than 25 IOs and still not at the 1...

Examples are available within ESP-IDF. The new driver is indeed quite different from the old one, but this needed to happen in order to support things like DMA; I don't know if the old driver supports that. Resolution of RMT Rx is the same as RMT Tx; with an 80MHz APB bus, you should be able to capt...

The bootloader that is responsible for flashing the chips is baked into ROM in the factory in case of ESP32 chips: you do not have to (and in fact cannot) flash it; it works out of the box. On the C3, you can either use the serial port or the built-in USB to initially flash the chip. Note that if yo...

Generally, the ESP32 switches to download mode when the IO0 signal is low when EN goes from low to high. Do keep in mind that there's a RC network on EN, so if EN is released, it takes a fraction of a second to actually go high.

If your board confirms to the schematic, it's very unlikely that connecting both USB and battery, in whatever order, caused the ESP32 to smoke. There's a circuit that disables the battery when USB is connected, and even if that would fail, the result would be the battery being damaged and not the re...

Yes, that's correct. And from what I heard from the hardware team, the best way to 'terminate' it would be to simply leave the connection open.

So first of all: it'd be generally bad practice to create and destroy tasks like that: it's an expensive operation and you normally do it on startup only. For instance, you could have a doorTask which is created on startup and normally waits on some inter-task thing (a FreeRTOS semaphore or queue or...

FWIW, the way it works (a bit simpified) is that esp_task_wdt_reset only sets a flag that for this round, the associated task did reset their watchdog. There's a timer that periodically calls a routine that checks if all the registered tasks have done so, and if that's the case it feeds the hardware...

USB Mode: "Hardware CDC and JTAG" Component config → ESP System Settings → Channel for console output: USB Serial/JTAG Controller USB CDC On Boot: "Disabled" USB Firmware MSC On Boot: "Disabled" USB DFU On Boot: "Disabled" There's no direct equivalent as in ESP-IDF you'd have to initialize the USB-...