The document discusses real-time operating systems (RTOS) and FreeRTOS. It defines an RTOS as an OS intended for real-time applications that processes data without buffering delays. Popular RTOS include VxWorks, QNX Neutrino, FreeRTOS, and others. FreeRTOS is an open source RTOS kernel for embedded devices that provides task management, communication and synchronization primitives. It supports various architectures and is designed to be small, simple and provide low overhead.

1. ANKITA TIWARI
M.TECH(EST)-1ST YEAR
AMITY UNIVERSITY
Presented By

2. 2

3. What is RTOS?
 A real-time operating system (RTOS) is an operating
system intended to serve real-time application process data as
it comes in, typically without buffering delays. Processing
time requirements are measured in tenths of seconds or shorter.
3
 According to a 2015 Embedded Market Study..
•Green Hills Software INTEGRITY
•Wind River VxWorks
•QNX Neutrino
•FreeRTOS
•Micrium µC/OS-II, III
• etc

4. Architecture
RTOS
Executive
Scheduler
4

5.  In general, real-time operating systems are said to require:
• Multitasking
• Process threads that can be prioritized
• A sufficient number of interrupt levels
5
Why RTOS….

6. 6
Real-time operating systems are often required in small
embedded operating systems that are packaged as part of
microdevices.
Why RTOS….

7. 7
Some kernels can be considered to meet the requirements
of a real-time operating system. However, since other
components, such as device drivers, are also usually
needed for a particular solution, a real-time operating
system is usually larger than just the kernel.
Why RTOS….

8. What is FreeRTOS?
 FreeRTOS is a popular real-time operating
system kernel for embedded devices.
8
Developed by Real Time Engineers Ltd. and belongs to the
family of Real Time Operating System.
It is based on Microkernel type Kernel and licensed by
Modified GPL (GNU General Public License).

9. Implementation
 FreeRTOS is designed to be small and simple.
9
FreeRTOS provides methods for
multiple threads or tasks, mutexes, semaphores and software
timers.
A tick-less mode is provided for low power applications.

10. 10
Mutexes
Mutual exclusion is a property of concurrency control, which is
instituted for the purpose of preventing race conditions; it is the
requirement that one thread of execution never enter its critical
section at the same time that another, concurrent thread of
execution enters its own critical section
Semaphore
A semaphore is a variable or abstract data type that is used for
controlling access, by multiple processes, to a common resource
in a concurrent system such as a multiprogramming operating
system.

11. HOW CAN AN RTOS HELP US?
11

12.  Task management
 Task communication
• Message queues
 Task synchronization
• Binary semaphores
• Counting semaphores
• Mutexes
12

13. Task management
 portBASE_TYPE xTaskCreate( pdTASK_CODE pvTaskCode,
const portCHAR * const pcName,
unsigned portSHORT usStackDepth,
void *pvParameters,
unsigned portBASE_TYPE uxPriority,
xTaskHandle *pvCreatedTask );
pvTaskCode Pointer to the task entry function. Tasks must be implemented to
never return (i.e. continuous loop).
pcName A descriptive name for the task. This is mainly used to facilitate
debugging. Max length defined by configMAX_TASK_NAME_LEN.
usStackDepth The size of the task stack specified as the number of variables the
stack can hold - not the number of bytes. For example, if the stack is 16 bits
wide and usStackDepth is defined as 100, 200 bytes will be allocated for stack
storage. The stack depth multiplied by the stack width must not exceed the
maximum value that can be contained in a variable of type size_t.

14. pvParameters Pointer that will be used as the parameter for the task
being created.
uxPriority The priority at which the task should run.
pvCreatedTask Used to pass back a handle by which the created
task can be referenced.
void vTaskDelete( xTaskHandle pxTask );
pxTask The handle of the task to be deleted. Passing NULL
will cause the calling task to be deleted.

15.  void vTaskDelay( portTickType xTicksToDelay );
xTicksToDelay The amount of time, in tick periods, that the calling
task should block.
 void vTaskDelayUntil( portTickType *pxPreviousWakeTime,
portTickType xTimeIncrement );
pxPreviousWakeTime Pointer to a variable that holds the time at which the task
was last unblocked. The variable must be initialised with
the current time prior to its first use. Following this the
variable is automatically updated within
vTaskDelayUntil().
xTimeIncrement The cycle time period. The task will be unblocked at time
(*pxPreviousWakeTime + xTimeIncrement). Calling
vTaskDelayUntil with the same xTimeIncrement
parameter value will cause the task to execute with a
fixed interval period.

16. Task communication
 xQueueHandle xQueueCreate( unsigned portBASE_TYPE uxQueueLength,
unsigned portBASE_TYPE uxItemSize );
uxQueueLength The maximum number of items that the queue can
contain.
uxItemSize The number of bytes each item in the queue will require.
Items are queued by copy, not by reference, so this is the
number of bytes that will be copied for each posted item.
Each item on the queue must be the same size.
 void vQueueDelete( xQueueHandle xQueue );
xQueue A handle to the queue to be deleted.

17.  portBASE_TYPE xQueueSend( xQueueHandle xQueue,
const void * pvItemToQueue,
portTickType xTicksToWait );
xQueue The handle to the queue on which the item is to be
posted.
pvItemToQueue A pointer to the item that is to be placed on the queue.
The size of the items the queue will hold was defined when the queue was
created, so this many bytes will be copied from pvItemToQueue into the
queue storage area.
xTicksToWait The maximum amount of time the task should block
waiting for space to become available on the queue, should it already be full.
The call will return immediately if the queue is full and xTicksToWait is set to 0.
The time is defined in tick periods so the constant
portTICK_RATE_MS should be used to convert to real time if this is required.

18.  portBASE_TYPE xQueueReceive( xQueueHandle xQueue,
void *pvBuffer,
portTickType xTicksToWait );
xQueue The handle to the queue on which the item is to be posted.
pvBuffer Pointer to the buffer into which the received item will be
copied.
xTicksToWait The maximum amount of time the task should block
waiting for an item to receive should the queue be empty at the time of the
call. Setting xTicksToWait to 0 will cause the function to return immediately if
the queue is empty. The time is defined in tick periods so the constant
portTICK_RATE_MS should be used to convert to real
time if this is required.

19.  portBASE_TYPE xQueueSendFromISR( xQueueHandle pxQueue,
const void *pvItemToQueue, portBASE_TYPE
*pxHigherPriorityTaskWoken );
xQueue The handle to the queue on which the item is to be posted.
pvItemToQueue A pointer to the item that is to be placed on the queue.
The size of the items the queue will hold was defined when the queue was
created, so this many bytes will be copied from pvItemToQueue into the
queue storage area.
pxHigherPriorityTaskWoken
xQueueSendFromISR() will set *pxHigherPriorityTaskWoken to pdTRUE if
sending to the queue caused a task to unblock, and the unblocked task has a
priority higher than the currently running task. If xQueueSendFromISR() sets
this value to pdTRUE then a context switch should be requested
before the interrupt is exited.

20.  portBASE_TYPE xQueueReceiveFromISR( xQueueHandle pxQueue,
void *pvBuffer,
portBASE_TYPE *pxTaskWoken );
xQueue The handle to the queue on which the item is to be posted.
pvBuffer Pointer to the buffer into which the received item will be
copied.
pxTaskWoken A task may be blocked waiting for space to become available on
the queue. If xQueueReceiveFromISR causes such a task to unblock
*pxTaskWoken will get set to pdTRUE, otherwise *pxTaskWoken will
remain unchanged.

21. Task synchronization
 vSemaphoreCreateBinary( xSemaphoreHandle xSemaphore )
xSemaphore Handle to the created semaphore. Should be of type
xSemaphoreHandle.
 xSemaphoreHandle xSemaphoreCreateCounting(
unsigned portBASE_TYPE uxMaxCount,
unsigned portBASE_TYPE uxInitialCount )
uxMaxCount The maximum count value that can be reached. When the
semaphore reaches this value it can no longer be 'given'.
uxInitialCount The count value assigned to the semaphore when it is created.
 xSemaphoreHandle xSemaphoreCreateMutex( void )

22.  xSemaphoreTake( xSemaphoreHandle xSemaphore,
portTickType xBlockTime )
xSemaphore Handle to the created semaphore. Should be of type
xSemaphoreHandle.
xBlockTime The time in ticks to wait for the semaphore to become
available. The macro portTICK_RATE_MS can be used to convert this
to a real time. A block time of zero can be used to poll the semaphore.
 xSemaphoreGive( xSemaphoreHandle xSemaphore )
xSemaphore A handle to the semaphore being released. This is the
handle returned when the semaphore was created.

23.  xSemaphoreGiveFromISR( xSemaphoreHandle xSemaphore,
signed portBASE_TYPE *pxHigherPriorityTaskWoken )
xSemaphore Handle to the created semaphore. Should be of type
xSemaphoreHandle.
pxHigherPriorityTaskWoken xSemaphoreGiveFromISR() will set
*pxHigherPriorityTaskWoken to pdTRUE if giving the semaphoree caused a
task to unblock, and the unblocked task has a priority higher than the
currently running task. If xSemaphoreGiveFromISR() sets this value to pdTRUE
then a context switch should be requested before the interrupt is exited.

24. void EXTI_IRQHandler(void)
{
portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE; // local var.
if(EXTI_GetITStatus(EXTI_Line10) != RESET)
{
EXTI_ClearITPendingBit(EXTI_Line10);
xSemaphoreGiveFromISR(Semaphore1, & xHigherPriorityTaskWoken);
portEND_SWITCHING_ISR( xHigherPriorityTaskWoken ); // must have
}
}
Example of interrupt function

25. Supported Architecture
• Altera Nios II
• ARM architecture
– ARM7
– ARM9
– ARM Cortex-M0
– ARM Cortex-M0+
– ARM Cortex-M3
– ARM Cortex-M4
– ARM Cortex-M7
– ARM Cortex-A
25
• AtmelAtmel
AVR
-- AVR32
-- SAM3
-- SAM4
-- SAM7
-- SAM9
-- SAM D20
-- SAM L21
• Intel
-- x86
-- 8052
• Freescale
-- Coldfire V1
-- Coldfire V2
-- HCS12
-- Kinetis
• IBM
-- PPC405
-- PPC404
• Infineon
-- TriCore
-- Infineon XMC4000

26. RELATED PROJECTS…
26

27. 27
 SafeRTOS
• SafeRTOS was constructed as a complementary offering to
FreeRTOS, with common functionality but with a uniquely
designed safety-critical implementation.
• SafeRTOS is known for its ability, unique among Operating
Systems, to reside solely in the on-chip read only memory of a
microcontroller.

28. 28
• The commercial licensing terms for OpenRTOS remove all
references to the GNU General Public License (GPL).
• Another project related to FreeRTOS, one with identical code
but different licensing & pricing, is OpenRTOS from the
commercial firm WITTENSTEIN Aerospace and Simulation
Ltd.
 OpenRTOS

29. 29