Have you configure the target for ESP32S3 ? 1. Delete existing build folder 2. Use the ESP-IDF: Set Espressif device target command 3. Use the ESP-IDF: Select OpenOCD Board Configuration command to choose openOCD board or interface to use. You can also look at the troubleshooting guide to understand...

This should be fixed in v1.6.1. Please take a look

QEMU is only available for ESP32. Other chips are not yet supported.

You could either configure the extension manually by having everything in the offline computer already.

JSON Manual Configuration

Or you could use a previously configured Docker container or WSL environment as shown in the tutorial here:

Docker container tutorial

WSL tutorial

If the option is not visible in menuconfig is probably because it depends on another configuration that hides this value. When the build happens there is a configuration validation that will use a default value if another configuration is disabled.

How are you setting the target to esp32c6 ? We haven't add support for it in the vscode extension yet.

Probably because the toolchain_prefix is defined based on target and is a null string for anything else. Should fix this in the extension soon.

Seems there might be an issue with your configuration. Check the troubleshooting section and share the required information.

The [Scan for kits] message is from the CMake Tools extension, not the Espressif VSCode extension. Your c_cpp_properties.json seems to be configured. These message you are receiving can be removed by uninstalling this extension. "compileCommands": "${workspaceFolder}/build/compile_commands.json" is ...

I see the issue now. You have defined "initGdbCommands": [ "target remote :3333", "symbol-file /build/VimmsLite_main.elf", "mon reset halt", "flushregs", "thb app_main", "c" ] and as specified in the debugging documentation but initGdbCommands doesn't need to be defined by default. The error in the ...

It seems something went wrong after switching threads in your application. In your .vscode/launch.json could you change your logLevel to 4 to increase the output from debug adapter. This should give us a bit more detail about the error. You could also play with the tmoScaleFactor to increase the wai...