I have an interrupt service routine that gets data, places it into memory, then sends a message to an associated task that the data is ready. I recently found that I could also use OS_WakeTask( ) to immediately have that task process the data. At the end of that task, I have a OS_Delay( ) - do I really need the delay any more, if the task can be awakened directly by its associated interrupt service routine?
When I commented out the OS_Delay, I found that a task that blinks an LED (to let me know that the OS is working) - stopped, until I raised the priority to match the task using OS_WakeTask( ).
Hopefully, I have made this clear...
I could keep the OS_Delay in the task code, just put a huge delay - have not tried that yet. What was confusing was why the LED task essentially stopped...
Regards,
Todd Anderson
When I commented out the OS_Delay, I found that a task that blinks an LED (to let me know that the OS is working) - stopped, until I raised the priority to match the task using OS_WakeTask( ).
Hopefully, I have made this clear...
I could keep the OS_Delay in the task code, just put a huge delay - have not tried that yet. What was confusing was why the LED task essentially stopped...
Regards,
Todd Anderson