Question about MQX Task States

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Question about MQX Task States

跳至解决方案
4,000 次查看
george
Senior Contributor II

Hi all,

I'm investigating the dead-lock possibility of MQX Task.

Because, my customer wants to know it.

I have any question about MQX Task States.

I want to tell me about the condition of indicating with Blue in an attached file.

PRI_20121228181254.bmp

Best Regards,

George

标记 (4)
0 项奖励
回复
1 解答
3,391 次查看
JuroV
NXP Employee
NXP Employee

Yes, if a task is waiting for a resource, it is in the BLOCKED state.After acquiring the resource, it goes to the READY state, or to the ACTIVE state afterwards (depends on situation).

在原帖中查看解决方案

0 项奖励
回复
4 回复数
3,391 次查看
JuroV
NXP Employee
NXP Employee

Hello George,

I am trying to understand your question.

If TaskA is waiting for semaphore that is currently owned by TaskB and TaskB is waiting for event that can be signalled by TaskA, then the deadlock occurs.

Is that what you wanted to know?

0 项奖励
回复
3,391 次查看
george
Senior Contributor II

Thanks Juraj,

I understood the example which a deadlock occurs.

The condition which indicates in the light blue in an attached file should tell to which of (1)-(6) it corresponds.

When a Task is kept waiting by Mutex, Semaphore and Event, is a Task in Blocked?

Best Regards,

George

0 项奖励
回复
3,392 次查看
JuroV
NXP Employee
NXP Employee

Yes, if a task is waiting for a resource, it is in the BLOCKED state.After acquiring the resource, it goes to the READY state, or to the ACTIVE state afterwards (depends on situation).

0 项奖励
回复
3,391 次查看
george
Senior Contributor II

Thanks Juraj,

0 项奖励
回复