![](http://pdfasset.owneriq.net/9/fb/9fbfa399-be01-4490-812f-c791db5ef399/9fbfa399-be01-4490-812f-c791db5ef399-bg37.png)
- 41 -
• Forcibly resume suspended task (frsm_tsk, ifrsm_tsk)
Clears the number of suspension requests nested to 0 and forcibly resumes execution of a task. Since MR100 al-
lows only one suspension request to be nested, this service call behaves the same way as rsm_tsk and
irsm_tsk..(See Figure 4.8).
READYstate
frsm_tsk
0 1 0
Number of
suspension
requests
Task
sus_tsk
READY state
SUSPENDED
state
WAITING
state
WAITING state
WAITING
–
SUSPENDED
state
Figure 4.8 Forcible wait of a task and forcible resume
• Release task from waiting (rel_wai, irel_wai)
Forcibly frees a task from WAITING state. A task is freed from WAITING state by this service call when it is in
one of the following wait states.
♦ Timeout wait state
♦ Wait state entered by slp_tsk service call (+ timeout included)
♦ Event flag (+ timeout included) wait state
♦ Semaphore (+ timeout included) wait state
♦ Message (+ timeout included) wait state
♦ Data transmission (+ timeout included) wait state
♦ Data reception (+ timeout included) wait state
♦ Fixed–size memory block (+ timeout included) acquisition wait state
♦ Short data transmission (+ timeout included) wait state
♦ Short data reception (+ timeout included) wait state