crQUEUE_SEND macro

@code{c} crQUEUE_SEND( CoRoutineHandle_t xHandle, QueueHandle_t pxQueue, void *pvItemToQueue, TickType_t xTicksToWait, BaseType_t *pxResult ) @endcode The macro's crQUEUE_SEND() and crQUEUE_RECEIVE() are the co-routine equivalent to the xQueueSend() and xQueueReceive() functions used by tasks. crQUEUE_SEND and crQUEUE_RECEIVE can only be used from a co-routine whereas xQueueSend() and xQueueReceive() can only be used from tasks. crQUEUE_SEND can only be called from the co-routine function itself - not from within a function called by the co-routine function. This is because co-routines do not maintain their own stack. See the co-routine section of the WEB documentation for information on passing data between tasks and co-routines and between ISR's and co-routines. Example usage: @code{c} // Co-routine function that blocks for a fixed period then posts a number onto // a queue. static void prvCoRoutineFlashTask( CoRoutineHandle_t xHandle, UBaseType_t uxIndex ) { // Variables in co-routines must be declared static if they must maintain value across a blocking call. static BaseType_t xNumberToPost = 0; static BaseType_t xResult; // Co-routines must begin with a call to crSTART(). crSTART( xHandle ); for( ;; ) { // This assumes the queue has already been created. crQUEUE_SEND( xHandle, xCoRoutineQueue, &xNumberToPost, NO_DELAY, &xResult ); if( xResult != pdPASS ) { // The message was not posted! } // Increment the number to be posted onto the queue. xNumberToPost++; // Delay for 100 ticks. crDELAY( xHandle, 100 ); } // Co-routines must end with a call to crEND(). crEND(); } @endcode