TI E2E Community
Task is still in blocked mode even after Event_pend time out.
As titled, is this designed on purpose?
IMHO, when time out happens, the task continues its job (i.e. running). Its mode must reflect its real status: running instead of BLOCKED.
Following the timeout, the task mode should become READY. If that task is then the highest priority task in the system, then it's mode should become RUNNING.
Please describe how you are concluding that the timeout has occurred and that the task is running while in the BLOCKED state.
Yes, the problem is in my side.
It is wrong implementation in multiple tasks environment.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.