-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32S3 can no longer be debugged on Windows. #1299
Comments
Thanks for the report. We'll try to reproduce this. |
It may be unrelated (another ISSUE?), but maybe because Tinyusb is no longer installed by default with ESP-IDF v5, I can't build USE_USB=1 (for example, esp32/m5stamp_s3) properly. The message will be displayed as shown below.
thanks, |
Hello @NW-Lab, can you please try this patch for esp32-s3 devices? https://gist.github.com/mkellner/993ab3febf4f7dd951e3ba9473d88f76 |
mkellner san Thank you for your response. The tinyusb.h not found error is still there.(esp32/m5stamp_s3:USE_USB=1) Thank you. |
Thank you for your quick response. Please open a new issue for USE_USB=1 as it is indeed a different issue. |
I understand. |
hello
The program and xsbug will no longer be able to communicate on Windows.
It was probably used until around November.
The esp32s3 devices I have confirmed are esp32/m5atom_s3 and esp32/m5dial.
example/helloworld doesn't work.
The piu/balls screen is displayed, so the program seems to be running.
It is unclear whether it was when ESP-IDF was changed to v5.1.2 or when Moddable was updated.
It works fine with ESP32 (esp32/m5atom_matrix).
Console seems correct.
It is currently unknown whether the serial communication string for debugging is not output or there is a communication problem.
I haven't tried it yet on a non-Windows device.
thanks,
The text was updated successfully, but these errors were encountered: