Wokwi simulates very specific displays (ILI9341 and GDEH029A1). It might be possible to program something to match your display, but that is likely far more complicated than just plugging it in IRL. You can use Wokwi to get some experience with how the library works overall, but every piece of ...

What OS?
What version of Arduino IDE?
What version of arduino-esp32?
Are you directly following the directions and installing from the stable release link?
Explain a little better what happens when you click the install button. Does it start to download anything? It should download a series of files ...

I just have an idea of how a lot of this code is structured, and if the compiler complains that a function is not defined, but you can see where it is declared, and other functions in the same header work, then there is probably some config option blocking it out. 2 seconds browsing the code ...

Looks like the function is only included if CONFIG_MBEDTLS_X509_REMOVE_INFO is disabled.

Doco says 2 TWAI channels that are CAN FD capable (but not yet certified).

See the hardware design guidelines . The on-module primary crystal will be +-10ppm from 40MHz, but the RTC is fractional off that source, so will drift significantly if you are doing serious timekeeping.
You can add a 32.768kHz crystal (at an accuracy of your choosing) on gpio 32/33 to provide a ...

The SD_Test example demonstrates how to set the pins for non-default configurations.
If you have all 4 data lines connected on the SD, I'd recommend using SD_MMC, as SDIO will be much more performant than SPI.

Build a python virtual environment and test to see if the issue is directly in esptool. If so, post this issue at the esptool repo.

The location of the second stage bootloader varies depending on the variant (from boards.txt )
esp32c2.build.bootloader_addr=0x0
esp32c5.build.bootloader_addr=0x2000
esp32p4.build.bootloader_addr=0x2000
esp32h2.build.bootloader_addr=0x0
esp32c6.build.bootloader_addr=0x0
esp32c61.build.bootloader ...

Header says you need to set CONFIG_PRE_ENCRYPTED_OTA_USE_RSA.
Then, read your file containing a 3072 bit RSA private key in PEM format, and set the rsa_priv_key (and len) in cfg. You could also embed the key in your firmware as a literal string.