Question about MQX Task States

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Question about MQX Task States

ソリューションへジャンプ
2,818件の閲覧回数
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 解決策
2,209件の閲覧回数
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 返答(返信)
2,209件の閲覧回数
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 件の賞賛
返信
2,209件の閲覧回数
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 件の賞賛
返信
2,210件の閲覧回数
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 件の賞賛
返信
2,209件の閲覧回数
george
Senior Contributor II

Thanks Juraj,

0 件の賞賛
返信