Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
The documentation in rtos.h defined for ThreadX says the Networking worker thread has a lower priority than that of the Hardware IO thread. However, when I look at wiced_defaults.h the priorities are flipped. Is there is a reason there is an inconsistency ? The documentation talks about allowing IO to preempt network activity on the network thread which may take longer or block.
The FreeRTOS task defines the 0 is the lowest priority and priority increases as the priority value on thread creation increases.and ty abd priory increases.
The ThreadX implements the priorities as 0 being the highest thread priority level and the thread priority decreases as the priority value increases.
Wiced implements a wrapper for FreeRTOS and ThreadX. The thread priority for Wiced is 0 being the highest priority level. As the priority value increases on thread creation the actual thread priority decreases.