-
Notifications
You must be signed in to change notification settings - Fork 363
Fix some UART-related issues #4586
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
base: main
Are you sure you want to change the base?
Conversation
|
/hil full |
|
Triggered full HIL run for #4586. Run: https://github.com/esp-rs/esp-hal/actions/runs/19830655480 Status update: ❌ HIL (full) run failed (conclusion: failure). |
4ad6928 to
bed8a12
Compare
38406fe to
2be16bc
Compare
2be16bc to
ef47d58
Compare
ef47d58 to
6c02337
Compare
|
/hil full |
|
Triggered full HIL run for #4586. Run: https://github.com/esp-rs/esp-hal/actions/runs/19865042209 Status update: ❌ HIL (full) run failed (conclusion: failure). |
fd07a6e to
1f46865
Compare
|
I just tested the current commit of your branch |
|
Thank you, I'll spend time to try and better reproduce this issue. In the mean time, can you try changing the |
This PR makes three changes to the UART driver:
It stabilizesWill be proposed separately.read_readyand expands on its documentation, to make it possible to truly read without blocking.wait_for_buffered_datain an attempt to fixread_exact_asyncreturnsFifoOverflowedwhen more than 128 bytes is to be received #4523@jimy-byerley could you please see if this PR addresses your issue? It's not easy to reproduce on the MCU itself, and I'm not sure if we can make a reliable test case for it.