Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


configASSERT fail on xQueueSendFromISR

Posted by joe_her on November 1, 2014

Trying to figure out why this happens, according to the comments in the code,: /* The following assertion will fail if a service routine (ISR) for an interrupt that has been assigned a priority above configMAXSYSCALLINTERRUPTPRIORITY calls an ISR safe FreeRTOS API function. ISR safe FreeRTOS API functions must only be called from interrupts that have been assigned a priority at or below configMAXSYSCALLINTERRUPTPRIORITY.
... */

so I changed this HALNVICSetPriority to configMAXSYSCALLINTERRUPTPRIORITY, but it still fail. This code is part of USB host, for STM32F4, code is the library by ST. //--------------- HALNVICSetPriorityGrouping(NVICPRIORITYGROUP4); HALNVICSetPriority(OTGFSIRQn, configMAXSYSCALLINTERRUPTPRIORITY, 0); HALNVICEnableIRQ(OTGFSIRQn); //---------------- Any ideas and tips how to debug this will help. Thanks.

configASSERT fail on xQueueSendFromISR

Posted by rtel on November 1, 2014

configMAXSYSCALLINTERRUPTPRIORITY is probably a full 8 bit value, whereas NVICSetPriority() requires a shifted priority. I know this is complex but it is how the Cortex-M works. I tried explaining it on this page: http://www.freertos.org/RTOS-Cortex-M3-M4.html

Most newer projects have a conversion in the FreeRTOSConfig.h file, something like the following:

/* Cortex-M specific definitions. */
	/* __BVIC_PRIO_BITS will be specified when CMSIS is being used. */
	#define configPRIO_BITS       		__NVIC_PRIO_BITS
	#define configPRIO_BITS       		4        /* 15 priority levels */

/* The lowest interrupt priority that can be used in a call to a "set priority"
function. */

/* The highest interrupt priority that can be used by any interrupt service
routine that makes calls to interrupt safe FreeRTOS API functions.  DO NOT CALL
PRIORITY THAN THIS! (higher priorities are lower numeric values. */

/* Interrupt priorities used by the kernel port layer itself.  These are generic
to all Cortex-M ports, and do not rely on any particular library functions. */
/* !!!! configMAX_SYSCALL_INTERRUPT_PRIORITY must not be set to zero !!!!
See http://www.FreeRTOS.org/RTOS-Cortex-M3-M4.html. */

So in that case configLIBRARYLOWESTINTERRUPTPRIORITY is set by hand as a shifted value (and therefore easier to understand for a human) and configKERNELINTERRUPTPRIORITY is then generated automatically. Likewise configLIBRARYMAXSYSCALLINTERRUPTPRIORITY and configMAXSYSCALLINTERRUPTPRIORITY.

The 'LIBRARY' prefix denoting that it is the version to be used in library function calls. So in your code you want to use configLIBRARYMAXSYSCALLINTERRUPTPRIORITY to prevent the assert triggering.


configASSERT fail on xQueueSendFromISR

Posted by joe_her on November 2, 2014

I read the page at http://www.freertos.org/RTOS-Cortex-M3-M4.html as it is in the comment above the assert line, but did not understand that I need to use configLIBRARYLOWESTINTERRUPT_PRIORITY.

This solved the problem.

Thank you.

[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]

Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


FreeRTOS and other embedded software careers at AWS.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers


STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner