# Some task unexpected stops

**URL:** <https://forums.freertos.org/t/some-task-unexpected-stops/2330>\
**Category:** Kernel\
**Created:** [August 15, 2014, 7:27am UTC](https://forums.freertos.org/t/some-task-unexpected-stops/2330 "2014-08-15T07:27:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [August 15, 2014, 7:27am UTC](https://forums.freertos.org/t/some-task-unexpected-stops/2330/1 "2014-08-15T07:27:14Z")

</div>

**[sminder](https://sourceforge.net/u/sminder/)** wrote on [Friday, August 15, 2014](https://sourceforge.net/p/freertos/discussion/382005/thread/6aa5d8cf/#c343):

I have a number tasks and they run fine as long as something does happen. Then some tasks has “Ready” state and highest priority but never executed, and some task have less priority but executed. The table of the states of tasks is given below:

TskNum&nbsp;&nbsp;TskName&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Prio&nbsp;&nbsp;&nbsp;&nbsp;TskStatus  
7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IDLE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ready  
5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_buf&nbsp;&nbsp;&nbsp;&nbsp;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ready  
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_keys&nbsp;&nbsp;&nbsp;3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Running  
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_zb&nbsp;&nbsp;&nbsp;4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ready  
8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tmr&nbsp;Svc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Blocked  
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_ptt&nbsp;&nbsp;&nbsp;&nbsp;3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Suspended  
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_led&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Suspended  
6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;task\_usb&nbsp;&nbsp;&nbsp;&nbsp;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Suspended

I’m interested in a “task\_zb” task which has a highest priority and the “Ready” state but never executed. At the same time the “task\_keys” task which has less priority running as well as an “IDLE” task (the “task\_buf” task also never executed).  
That the problem?

P.S. RTOS port is ARM Cortex M3, version is 7.4.2

---

<div class="post-metadata">

**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\
**Post date:** [August 15, 2014, 8:16am UTC](https://forums.freertos.org/t/some-task-unexpected-stops/2330/2 "2014-08-15T08:16:35Z")

</div>

**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Friday, August 15, 2014](https://sourceforge.net/p/freertos/discussion/382005/thread/6aa5d8cf/#adbc):

This is normally a symptom of incorrect interrupt priority assignments. I would recommend updating your FreeRTOS version, ideally to V8.0.1 (should just be a drop in replacement), but at least to one of the later V7.x.x versions, then ensure [configASSERT()](http://www.freertos.org/a00110.html#configASSERT) is defined. This is because the latest versions have additional assert calls specifically designed to trap interrupt priority issues.

You can also look through the [My application does not run](http://www.freertos.org/FAQHelp.html) section of the FAQ to ensure you are also complying with the normal API usage requirements.

Regards.

---

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [August 22, 2014, 7:25am UTC](https://forums.freertos.org/t/some-task-unexpected-stops/2330/3 "2014-08-22T07:25:04Z")

</div>

**[sminder](https://sourceforge.net/u/sminder/)** wrote on [Friday, August 22, 2014](https://sourceforge.net/p/freertos/discussion/382005/thread/6aa5d8cf/#cffd):

Thanks a lot for your advice! I just replaced my old RTOS version by a new one and I’ve got a great tool for the interrupt priority diagnosis so I found the problem.
