problem with semaphore

nobody wrote on Friday, March 10, 2006:

look at the following sample code:


Obviously, the vTaskDelay(1) shoudn’t be executed.

In my case, is executed!!

Can someone help me?
I am using arm7 at91sam7a3 cpu.

Thenks a lot.

nobody wrote on Friday, March 10, 2006:

There was a thread about this recently.  You might want to look it up.

It can be that you block waiting to get a semaphore.  The semaphore becomes available and unblocks the task.  Because of the prioritization of your tasks the unblocked task although now able to run does not run before another task has again taken the semaphore.  When the unblocked task does run it finds the semaphore already gone again and returns false.

There are a couple of ways around this.  Change the prioritisation of your tasks so this cannot happen.  Change the test to see if a switch should happen to say a switch occurs if a woken task has a priority greater or equal to the current task (by default a switch is performed if the woken task is *greater* than the current task only).  Finally put the call to xSemaphoreTake within a while statement as:

while( xSemaphoreTake(semaphore1,portMAX_DELAY) != pdTRUE );

The while will only exit when the semaphore was successfully taken no matter what the other priorities within your system.

nobody wrote on Monday, March 13, 2006:

Using the ‘while’ solution it seems working!!

Thank you a lot for your time.