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
when the function tud_task() is called, it will in its turn call tud_task_ext(UINT32_MAX, false). The problem with this is that if there are no more messages in the freertos queue, the timeout value of UINT32_MAX is like stay here forever.. and system hangs. I think the value of timeout could be set to 0 to immediatly return if there is no data available in the queue.
How to reproduce ?
try to comile a cdc example with stm32u5 and freertos configured.
Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
I dont have any logs.
Screenshots
No response
I have checked existing issues, dicussion and documentation
I confirm I have checked existing issues, dicussion and documentation.
The text was updated successfully, but these errors were encountered:
I still have to add a vTaskDelay after tud_task() function otherwise my application freezes. And what I dont understand is if the tud_task is blocking, it is consuming all cpu right?? How is it supposed to work?
Ok thats clear to me , but why is my application only working properly with the vTaskDelay added? It should work without it right? But it doesnt. Are there other FreeRTOS config settings which can cause this behaviour?
Operating System
Linux
Board
Custom
Firmware
custom firmware
What happened ?
when the function tud_task() is called, it will in its turn call tud_task_ext(UINT32_MAX, false). The problem with this is that if there are no more messages in the freertos queue, the timeout value of UINT32_MAX is like stay here forever.. and system hangs. I think the value of timeout could be set to 0 to immediatly return if there is no data available in the queue.
How to reproduce ?
try to comile a cdc example with stm32u5 and freertos configured.
Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
I dont have any logs.
Screenshots
No response
I have checked existing issues, dicussion and documentation
The text was updated successfully, but these errors were encountered: