Quality RTOS & Embedded Software

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




Loading

The difference between xEventGroupSync() and xEventGroupWaitBits()?

Posted by murajin on July 2, 2014

These two functions seem to behave in a similar way. And it looks like that with using xEventGroupWaitBits(), you can make the RTOS behave the same way as using xEventGroupSync(). (by setting xClearOnExit parameter to pdTRUE and xWaitForAllBits to pdTRUE) Am I missing something? Or is there another function in xEventGroupSync() that I didn't understand?


The difference between xEventGroupSync() and xEventGroupWaitBits()?

Posted by rtel on July 2, 2014

xEventGroupsSync() sets bits then waits for bits.

xEventGroupWaitBits() only waits for bits.

So the two functions are quite different.

xEventGroupSync() is equivalent to calling xEventGroupSetBits() bits followed by a call to xEventGroupWaitBits() BUT does it in an atomic way. Calling the two functions separately to try and effect what is commonly called a task rendezvous will not work because of the race conditions it creates - hence you use xEventGroupSync() instead. Many other RTOSes that don't have this atomic set then wait capability.

Regards.


The difference between xEventGroupSync() and xEventGroupWaitBits()?

Posted by jdurand on July 2, 2014

So is Wait is the same as calling Sync without setting any bits.

Attachments

alternate (2331 bytes)

The difference between xEventGroupSync() and xEventGroupWaitBits()?

Posted by rtel on July 2, 2014

Not really. It does not make sense to call Sync without setting any bits, so in a real world example they can't really be considered as equivalent. I suppose you could call Sync without setting any bits, but why would you if you can set the parameters of the Wait function to do the same thing in a more efficient way?

Regards.


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




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

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

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

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

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists