Quality RTOS & Embedded Software

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




Loading

<, or <= ?? configMAX_SYSCALL_INTERRUPT_PRIORITY

Posted by dnadler on August 25, 2016

Hi Richard ! I got an assertion when I forgot to set an interrupt's priority (thanks for that!). I set it to configMAXSYSCALLINTERRUPT_PRIORITY and the code no longer asserts. However, the comments in FreeRTOS and documentation are approximately as follows:

~~~ // ISRs using FreeRTOS APIs (for example, USB CDC driver uses FreeRTOS queues) must have priority // logically lower (numerically higher) than configMAXSYSCALLINTERRUPTPRIORITY. // For an interrupt priority to be lower than configMAXSYSCALLINTERRUPTPRIORITY, // it must be numerically higher than configMAXSYSCALLINTERRUPT_PRIORITY, because on the // ARM Cortex-M3 numerically low priority values represent logically high interrupt priorities. ~~~

Should the comments/documentation read "less than or equal to"? Or should the code be asserting if I do the following? NVICSetPriority (USBIRQn, configMAXSYSCALLINTERRUPT_PRIORITY);

Thanks as always, Best Regards, Dave


<, or <= ?? configMAX_SYSCALL_INTERRUPT_PRIORITY

Posted by rtel on August 25, 2016

You are right, it should say less that or equal to.


<, or <= ?? configMAX_SYSCALL_INTERRUPT_PRIORITY

Posted by dnadler on August 28, 2016

Thanks Richard!


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




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

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

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