FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [August 2016 Threads]
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
You are right, it should say less that or equal to.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.