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


FreeRTOS V8.2.0 release candidate available

Posted by rtel on December 24, 2014

Hello everybody.

After much effort a release candidate for FreeRTOS V8.2.0 has been made available for download. It is still in test, but in the mean time all comments and feedback will be greatly appreciated.

A change history is available, and the new direct to task notification mechanism is of particular note.


FreeRTOS V8.2.0 release candidate available

Posted by rtel on December 27, 2014

FreeRTOS V8.2.0 release candidate available

Posted by heinbali01 on December 28, 2014

Hi all,

  • Where has FreeRTOS-Plus-TCP gone ?

Some people may wonder why the FreeRTOS V8.2.0 release only contains the earlier UDP library:

~~~~~ FreeRTOSV8.1.2/FreeRTOS-Plus/Source/FreeRTOS-Plus-UDP ~~~~~

and not +TCP? Whereas FreeRTOS-Plus-TCP is also a "Plus" product?

That is because +TCP is still in the Labs. Several users are helping us to test +TCP on several platforms. We have been testing it on Zynq, LPC18xx, and UC3A/SAM4E, and in the Windows' RTOSDemo.

In January we'll give extra attention to +TCP drivers for STM32F boards. Any updates of the drivers will be announced in this list and appear on:


Of course +TCP also includes other protocols like ARP, ICMP, UDP, and some higher protocols like DHCP, DNS, LLMNR, and NBNS.

  • Some people will remember the earlier post FreeRTOS eating memory :


In fact FreeRTOS wasn't eating memory, but for some situations the implementation of queues and semaphores was maybe "over complete".

FreeRTOS' queues and semaphores can have many givers and many receivers. Their behaviour is deterministic (and therefore predictable) under all circumstances. That is all great but it makes them more expensive than other mechanisms / implementations.

It was around that time that the idea for the "task notification mechanism" was born. It has a single receiver and it may still have multiple givers. Beside being deterministic, the mechanism is fast and very economic.

I think that many semaphores can actually be replaced by "task notification".

E.g. an SPI interrupt can call vTaskNotifyGiveFromISR() to wake up the task waiting for SPI.


[ 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