-
Notifications
You must be signed in to change notification settings - Fork 236
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
Serial not works on ESP-IDF5 #1367
Comments
This might not be a bug. You are using a debug build. On Moddable Two, that means that pins 1 and 3 are reserved for xsbug communication. Those pins are the default for a new serial connection, so the echo example is trying to use them. The Moddable SDK was updated some time ago to reserve the pins used by xsbug so that a project cannot interfere with the xsbug communication. Please try using an instrumented build ( |
This issue has been idle for a bit. Is there an update? |
I’m sorry for the delayed report. The situation is stuck, and using the instrumented build or setting |
I looked into this a bit more. I used Moddable Two, since that was listed in your report. For a debug build, using the default pins throws an exception as expected. Changing them (I used 16 for transmit and 17 for receive) does not throw an exception (as expected). For an instrumented build, no exception is thrown with the default pins. But... it does seem to hang - at least the serial port is not responding. Changing the After some further experimentation, it seems that in IDF v5 port 2 is incompatible with the default pins (transmit 1 and receive 3). |
Instrumented build + using port 1 is works as expected. |
Build environment: macOS
Moddable SDK version: 3bf5202
Target device: M5Stack, M5Stack_core2, Moddable_two
Steps to Reproduce
examples/io/serial/echo
using this build command:mcconfig -d -m -p esp32/m5stack
Logs & Console
Device keeps restarting.
Other information
It works in Moddable V4.1 and ESP-IDF v.4.2.3, so it seem to be affected by updating to ESP-IDF v5
The text was updated successfully, but these errors were encountered: