-
Notifications
You must be signed in to change notification settings - Fork 70
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
Communication stuck if connecting to one UART only #20
Comments
Did you try updating the pico SDK to HEAD? It includes lots of fixes, probably might fix it for you. |
I was also able to recreate the same problem here on Linux, but there's specific conditions to trip the problem. The communication packets have actually started, then stopped from the PC side... This is caused by two bugs. Basically the code spins waiting to unblock, which will never happen until the host catches up, it never will. Basically it gets stuck because... The fix is to remove the infinite loop by dropping the UART data on the floor. |
Try this version and let me know if it works.
It is also possible to send breaks with this firmware. |
@xxxajk it would help a lot if you could provide the modified source code with the fixes. |
Done. |
Thanks!
Yes, please, open a new PR with this |
Are you OK with the different pin setup? |
I can confirm that #25 fixes the issue 🎊 |
Glad someone cherry picked it. |
First of all, kudos for the project.
I have a device exposing two UARTS and I connect both the serials to the PICO.
I noticed that if I open a serial session (I use
screen
on macOS) to one UART only (either one of the two), the communication stuck after few bytes exchanged.If I open the connection to the second UART, while the first one is frozen, the connection is resumed on both.
Please see attached screen recording.
Screen.Recording.2024-02-04.at.15.50.09.mov
The text was updated successfully, but these errors were encountered: