Semaphore and SPI interuppt

anonymous wrote on Monday, April 11, 2011:

Hi,

I am using LM3SXXXX MCU. I used SPI to receive data.  I set ISR to check receive data interrupt. When interrupt occur , it call my read data task.
I defined semaphore in main like

/* Create the semaphore used to wake the Read Data task from the SPI
ISR. */
vSemaphoreCreateBinary( xSPISemaphore );
xSemaphoreTake( xSPISemaphore, 0 );

-------------------ISR code ------------------------
void vSSI_ISR(void)
{
unsigned portLONG ulStatus;
ulStatus = SSIIntStatus( SSI_BASE, pdTRUE );
SSIIntClear( SSI_BASE, ulStatus );

if( ulStatus & SSI_RXTO )
{

if( xSemaphoreGiveFromISR( xSPISemaphore, pdFALSE ) )
{
portEND_SWITCHING_ISR( pdTRUE );
}
}

My read data task

for( ;; )
    {
   
/* Wait for a SSI RX interrupt to wake this task. */
while( xSemaphoreTake( xSPISemaphore, portMAX_DELAY ) != pdPASS );

  and then read code algorithm……

}

When i start first, it work fine for single time execution .But second time when interrupt occur …But next time my  task is not block on Semaphore.,it should block . What is ur suggestion ?

anonymous wrote on Monday, April 11, 2011:

Some more inforamtion , when first time Interrupt come it work s perfect but when second time interrrupt come , In ISR routine ( xSemaphoreGiveFromISR( xSPISemaphore, pdFALSE ) )  , return errQUEUE_FULL instead of pdPass……

anonymous wrote on Monday, April 11, 2011:

By Richard barry"Yes - semaphores are built on top of queues, so when you get the errQUEUE_FULL return value it means the semaphore cannot be given because it is already there. For example, if it is a binary semaphore, you can take the semaphore successfully, then give it successfully once. Once it is given the semaphore is effectively ‘full’. If you attempt to give it again without first taking it again you will get this error code returned. "

I also tried to take semaphore back by xSemaphoreTake( xSPISemaphore, 0 );
at the end of the of task which ISR calling.Still same problem….

edwards3 wrote on Monday, April 11, 2011:

Are you sure the interrupt is being cleared properly and not just continuously executing?
Have you stepped through the code after the first successful xSemaphoreTake() to check the rest of the code is working as you think?
Consider using a counting semaphore instead, in case interrupts are coming in too quickly for the binary use.

anonymous wrote on Monday, April 11, 2011:

Yes interrupt occur second time, i wrote a problem ,
xSemaphoreGiveFromISR( xSPISemaphore, pdFALSE ) )  , return errQUEUE_FULL instead of pdPass……