Stm32 uart async driver changes offset after callback #31973
Assignees
Labels
bug
The issue is a bug, or the PR is fixing a bug
platform: STM32
ST Micro STM32
priority: low
Low impact/importance bug
Comments
erwango
added
platform: STM32
jasuramme
added a commit
to jasuramme/zephyr
that referenced
this issue
Feb 4, 2021
Fixes the bug when driver changes offset after the callback call. When you have the ready event you suppose no changes in driver data after that. Fixes zephyrproject-rtos#31973 Signed-off-by: Alexander Shuklin <[email protected]>
nashif
pushed a commit
that referenced
this issue
Feb 4, 2021
Fixes the bug when driver changes offset after the callback call. When you have the ready event you suppose no changes in driver data after that. Fixes #31973 Signed-off-by: Alexander Shuklin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Stm32 uart async driver changes itself state (offset data) after calling the callback function with rx_ready event.
If you try to restart rx receive (for example, change buffer just after rx_ready event), you will have bad offset data (should be equal to zero)
To Reproduce
Call uart->rx_enable from uart async callback
Expected behavior
Driver shouldn't change itself state after ready event
Impact
You cannot run rx_enable from uart callback
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: