Inconsistant Documentation Of xTicksToWait In `Direct To Task Notifications` - FreeRTOS

Quality RTOS & Embedded Software

Download FreeRTOS
Menu

NOTE:This is a read only archive of threads posted to the FreeRTOS support forum. Use these archive pages to search previous posts. New forum support threads can be started at the FreeRTOS forums.

FreeRTOS Support Archive

The FreeRTOS support forum can be used for active support both from Amazon Web Services and the community. In return for using our software for free, we request you play fair and do your bit to help others! Sign up for an account and 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. Use these archive pages to search previous posts. New forum support threads can be started at the FreeRTOS forums.

[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [July 2016 Threads]

Inconsistant Documentation Of xTicksToWait In `Direct To Task Notifications`

Posted by pmckinnis on July 25, 2016

The xTicksToWait parameter in ulTaskNotifyTake() and xTaskNotifyWait() doesn’t specify that portMAX_DELAY may be used to wait forever. So, is this supported? (I browsed the source, and It looks like it is). Either way, it probably makes sense to update the documentation of ulTaskNotifyTake() and xTaskNotifyWait() to clarify.

Inconsistant Documentation Of xTicksToWait In `Direct To Task Notifications`

Posted by rtel on July 25, 2016

Yes, in all the blocking APIs you can use portMAXDELAY to block indefinitely as long as INCLUDEvTaskSuspend is also set to 1. Thanks for the feedback, the web page will get updated.

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