Flashing via JTAG does not work when I change the port settings. The flasher does not detect that OpenOCD is running. Changing 'tcl port' back to 6666 fixes this.

I found another port setting in 'esp_debug_adapter': it defaults to 43474. Maybe this needs to be set differently, too?

P.S.: both configurations work in isolation.

Thank you for the quick reply! I tried to set up the two VSCode instances with different settings:

processor 1

'settings.json'
{
"idf.adapterTargetName": "esp32s3",
"idf.portWin": "COM71",
"idf.openOcdConfigs": [
"interface/ftdi/esp32_devkitj_v1.cfg",
"target/esp32s3.cfg"
],
"idf ...

I'm using VSCode on Windows with ESP-IDF v5.3.2. I have a custom board with two ESP32-S3s on it. I would like to debug both of them simultaneously using a single PC.

One processor is connected to the PC via the built-in USB-JTAG port, the other one is connected via an ESP-PROG JTAG programmer. Both ...

I try to reduce the power consumption of an ESP32-S3 by running only a single core. I've checked "Run FreeRTOS on on first core" in the FreeRTOS options. The log shows that the system is indeed running in single core mode, however, the current consumption does not change a bit. According to the ...

That seems to be a nicer solution indeed. However, then you'd need to add this component to all the components explicitly. While I could do it for my own components, it does not work with system or managed components like NimBLE or TinyUSB, I believe. On the other hand, the "include_directories ...

Now, how to do the same for ULP-RISCV components? Apparently the method above does not work with the RISCV compiler.

I have figured it out. Add
to the CMakeList.txt in the project's root directory, right before:

My intention is to keep all product-specific configuration header files in a single directory, for example, in the 'main/include' directory. I have several reusable (not product-specific) components that need to access these header files. I did not find any hint in the documentation about how to ...

Yes. However, there is only one integrated USB PHY on chip, so you would need an external PHY for the other function. See pp. 942. of the Technical Reference Manual v0.8.