You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
esp32s3 is not supported by Espressif QEMU. Only esp32 or esp32c3 targets are supported.
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
I confirm I have checked existing issues, online documentation and Troubleshooting guide.
The text was updated successfully, but these errors were encountered:
igrr
added
the
bug-report
Bug Report from users on Github (don't use this tag manually, its supposed to be used via the issue)
label
Jan 18, 2025
github-actionsbot
changed the title
Outdated information about supported QEMU targets
Outdated information about supported QEMU targets (VSC-1568)
Jan 18, 2025
OS
MacOS
Operating System version
not relevant
Visual Studio Code version
No response
ESP-IDF version
v5.4
Python version
not relevant
Doctor command output
not relevant
Extension
No response
Description
Trying to run QEMU on ESP32-S3 target with IDF v5.4 results in an error message that the target isn't supported, due to
vscode-esp-idf-extension/src/qemu/qemuManager.ts
Lines 150 to 158 in 7db3782
However, ESP32-S3 is supported in QEMU since https://github.com/espressif/qemu/releases/tag/esp-develop-9.0.0-20240606
I was going to suggest that we can get the list of supported targets from idf_tools.py, but then noticed that I actually forgot to add ESP32-S3 to the targets list for qemu-xtensa (https://github.com/espressif/esp-idf/blob/0f0068fff3ab159f082133aadfa9baf4fc0c7b8d/tools/tools.json#L891-L893) :) Will get that fixed on IDF side.
(Originally reported in espressif/qemu#115)
Debug Message
esp32s3 is not supported by Espressif QEMU. Only esp32 or esp32c3 targets are supported.
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: