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
Describe the bug
When using uarte_nrfx_poll_out and uarte_nrfx_tx from different threads in the same application,
the poll_out thread can block forever, and all calls to uarte_nrfx_tx will result in failure.
Both the poll_out and uart_tx threads should forever print out their respective messages.
The provided reproduction will instead print out 3 "I poll" messages before stopping forever.
Impact
Major annoyance
Environment (please complete the following information):
Zephyr 2.3rc1
The text was updated successfully, but these errors were encountered:
Describe the bug
When using uarte_nrfx_poll_out and uarte_nrfx_tx from different threads in the same application,
the poll_out thread can block forever, and all calls to uarte_nrfx_tx will result in failure.
This is a continuation of issue #22264
To Reproduce
I have pushed a commit based on Zephyr 2.3rc1 that demonstrates this issue on the blinky sample application.
https://github.com/JordanYates/zephyr/commit/87d296baca519294d28a8394f40022a42ef82991
Expected behavior
Both the poll_out and uart_tx threads should forever print out their respective messages.
The provided reproduction will instead print out 3 "I poll" messages before stopping forever.
Impact
Major annoyance
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: