Any reason for xQueueReceive not unblocking?

Hello everybody
just asking if someone knows any subtle reason that could prevents an xQueueReceive with infinite blocking time (portMAX_DELAY) to not return when the queue is filled with an xQueueSendToBackFromISR.

Short description:

  • a task (with a quite high prio) is blocking on an xQueueReceive;
  • an ISR triggered by an external signal wakes up the previous task with an xQueueSendToBackFromISR;
  • there is only one ISR that fills the queue and one task that consumes it (for the purpose to defer to the task a long computation);
  • the system (which has many other tasks) basically works, it can run for days (and the queue is filled each 1 ms), then without any reason, other evidences or ciclicity the xQueueReceive on the task stops to proceed when the ISR fills the queue;
  • I’ve verified (when the problem happens):
  • the interrupt is still executing (each 1 ms);
  • inside the ISR the call to xQueueSendToBackFromISR exit with retval != pdPASS;
  • I imagine that the queue is now full;
  • but the task waiting on the xQueueReceive is still present and in BLOCKED state;
  • i’m convinced that there are no other points where that task could be blocked, but of course bugs could be anywhere.

Already verified:

  • the queue has been created with success (and I don’t check with xQueueReceive if the queue pointer is void for any reason);
  • configASSERT is defined and working (when called…);
  • any other task (also at lower priority) is running and the FreeRTOS, in general, is healty;
  • rules for interrupt priorities are respected;

thank you for any suggestion
Alberto

Maybe the variable that holds the queue in the receiving task is being overwritten with something that is close enough to a real queue object not to generate a fault, or the queue structure itself is being “benevolently” overtrampled.

On thing you don’t mention is the ISR using the wasWoken flag to wake the task, but failing to do that should just delay the task till the next tick (assuming you have preemption enabled, which is by default).

The other issue sounds like corruption of system memory some how.

One question, what version of FreeRTOS are you using, older versions, even with configASSERT defined might let some errors sneek past. A typical issue that can cause this sort of issue is using FreeRTOS API inside an ISR with too high of a priority, or other similar configuration errors.

Hello Richard

yes, handled the yield stuff inside ISR.

should be 10.1.1. The target is Zynq7000.
Regarding the isr prio issue, i’ve checked that deliberately putting the prio at the wrong level correctly raises the assert inside FreeRTOS’s API.

Hello RAc

this is a good point. Now i’ve added a task that monitors the queue when there is the failure (printing " uxQueueMessagesWaiting" and the likes). Of course there is EMI noise around (is a motor control application) and staying connected with the jtag is not so practical.

thank you
Alberto

i cannot help but i basicly have the same problem on a renesas rx631

a basic system is running. i can run multiple tasks, the scheduler is working, semaphores aswell.

I have one queue which is filled by an RXIRQwith xQueueSendToBackFromISR() and portYIELD_FROM_ISR(). xQueueSendToBackFromISR returns true.
my irq has prio 4

#define configKERNEL_INTERRUPT_PRIORITY 1
#define configMAX_SYSCALL_INTERRUPT_PRIORITY 4

if i raise the prio of my irq above configMAX_SYSCALL_INTERRUPT_PRIORITY i also get the assert that my prio is wrong configured

the Task waits forever with xQueueReceive()

After leaving the irq handler the scheduler stops working and it seems like it always hangs at

if( listCURRENT_LIST_LENGTH( &( pxReadyTasksLists[ tskIDLE_PRIORITY ] ) ) > ( UBaseType_t ) 1 )

no other task is executed anymore(my blinky tasks stop working) and i don’t get into the irq handler again if i send other chars to the controller

i’m a little bit lost here. Used Freertos on stm32 before and never had such problems :confused:

how does your port implement the critical section?

on the rx631

void vTaskEnterCritical( void )
    {
        portDISABLE_INTERRUPTS();

        if( xSchedulerRunning != pdFALSE )
        {
            ( pxCurrentTCB->uxCriticalNesting )++;

            /* This is not the interrupt safe version of the enter critical
             * function so  assert() if it is being called from an interrupt
             * context.  Only API functions that end in "FromISR" can be used in an
             * interrupt.  Only assert if the critical nesting count is 1 to
             * protect against recursive calls if the assert function also uses a
             * critical section. */
            if( pxCurrentTCB->uxCriticalNesting == 1 )
            {
                portASSERT_IF_IN_ISR();
            }
        }
        else
        {
            mtCOVERAGE_TEST_MARKER();
        }
    }

Hello everybody
Sorry for my late reply.
If you refers to “taskENTER_CRITICAL()”, the Zynq7000 port (FreeRTOS Kernel V10.5.1) ends up here:

*void vPortEnterCritical( void )*
{
	/* Mask interrupts up to the max syscall interrupt priority. */
	*ulPortSetInterruptMask();*

	/* Now interrupts are disabled ulCriticalNesting can be accessed
	directly.  Increment ulCriticalNesting to keep a count of how many times
	portENTER_CRITICAL() has been called. */
	ulCriticalNesting++;

	/* This is not the interrupt safe version of the enter critical function so
	assert() if it is being called from an interrupt context.  Only API
	functions that end in "FromISR" can be used in an interrupt.  Only assert if
	the critical nesting count is 1 to protect against recursive calls if the
	assert function also uses a critical section. */
	if( ulCriticalNesting == 1 )
	{
		configASSERT( ulPortInterruptNesting == 0 );
	}
}

while “taskEXIT_CRITICAL” is after the #defines of the port:

*void vPortExitCritical( void )*
{
	*if( ulCriticalNesting > portNO_CRITICAL_NESTING )*
	{
		/* Decrement the nesting count as the critical section is being
		exited. */
		*ulCriticalNesting--;*

		/* If the nesting level has reached zero then all interrupt
		priorities must be re-enabled. */
		if( ulCriticalNesting == portNO_CRITICAL_NESTING )
		{
			/* Critical nesting has reached zero so all interrupt priorities
			should be unmasked. */
			portCLEAR_INTERRUPT_MASK();
		}
	}
}

Then “portCLEAR_INTERRUPT_MASK” is:

/* Macro to unmask all interrupt priorities. */
*#define portCLEAR_INTERRUPT_MASK()*									\
{																	\
	*portCPU_IRQ_DISABLE();*											\
	*portICCPMR_PRIORITY_MASK_REGISTER = portUNMASK_VALUE;*			\
	*__asm volatile (	"DSB		\n"*								\
						*"ISB		\n" );*							\
	*portCPU_IRQ_ENABLE();*											\
}

and:

	/* The critical section macros only mask interrupts up to an application
	determined priority level.  Sometimes it is necessary to turn interrupt off in
	the CPU itself before modifying certain hardware registers. */
	#define portCPU_IRQ_DISABLE()										\
		dmb();															\
		__asm__ __volatile__ ( "cpsid	i" ::: "memory" );				\
		dsb();															\
		isb();

	#define portCPU_IRQ_ENABLE()										\
		dmb();															\
		__asm__ __volatile__ ( "cpsie	i" ::: "memory" );			    \
		dsb();															\
		isb();

thanks

Can you examine pxReadyTasksLists for your task priority and see if the task is on ready list? Also, are you interrupts getting disabled somehow? Can you check the value of uxCriticalNesting in your task’s TCB?

Did you find anything from this?

hi @aggarg , no, for the moment the system is running and my counters don’t show anything strange. As I’ve told before, it’s a very rare occurrence - but still to catch.

Let us know whatever you find.

unfortunately as usual the error sat in front of the pc :frowning:

i switched from RX to GCC compiler and somehow the interrupt declaration of my pheripheral interrupt(where i access the queue) was wrong/missing and i think i missed a warning for a missing declaration.

everything compiled, the program seemed to be ok. multiple tasks where working fine. as soon as i jumped to my irq handler i could write to the queue but after i returned from it everything was garbage and i jumped elsewhere(sometimes the scheduler was quit, sometimes i hang at the described line in the scheduler.

so i think the compiler did not IRET and RET instead.

sorry for the hassle. this was absolutley my fault(but the description of the error felt the same to what i observed)
Regards

Glad that you figured. Thank you for reporting back!