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
Using version 0.17.0 of the esp-hal, and the code below, attempting to log using UART0 alongside println does not work.
Hardware behavior: Only "println output" is printed to the console with every loop iteration. The code was executed on the ESP32-C3 using the Rust DevKit. Wokwi behavior: No output printed at all. println works only if uart instantiation is removed.
If you're using the Rust board, it means you are printing via USB serial jtag, not uart.
The confusion here is that esp println is using the ROM code to print, which will also detect if the USB serial jtag is connected and output to there too (Note that this only applies to esp32c3 ROM code, the other chips don't do this) which is why you see the println! output. If you have a devkitC, you can take a look at the serial output from that and you'll see that this is working correctly.
Closing for now, but maybe we can do better to make it more clear what's happening in the future.
Using version 0.17.0 of the esp-hal, and the code below, attempting to log using
UART0
alongsideprintln
does not work.Hardware behavior: Only "println output" is printed to the console with every loop iteration. The code was executed on the ESP32-C3 using the Rust DevKit.
Wokwi behavior: No output printed at all.
println
works only ifuart
instantiation is removed.Update:
The same issue occurs when testing using the
embassy_serial
example in the esp-rs repo.The text was updated successfully, but these errors were encountered: