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


Code inside vs. outside tasks

Posted by on November 4, 2011

I have a general question regarding tasks. Let's say that I have non-RTOS code that I would like to convert to a FreeRTOS task. The existing code performs some initialization (e.g. HW setup) only at startup and then enters the main program loop. Now if I move the code to FreeRTOS I could put all the code as is including those initialization stiff inside a task function or I could try to isolate the init stuff into my main() so that it runs before the scheduler is started. Only the main program loop would then go into the task function. Are there any benefits (e.g. resource saving) that are worth that additional program modification? Thank you in advance for the clarification.


RE: Code inside vs. outside tasks

Posted by Dave on November 4, 2011
Normally hardware would be set up before the scheduler was started. You can disable interrupts if necessary, as they will be automatically be re-enabled when the first task starts.

RE: Code inside vs. outside tasks

Posted by on November 4, 2011
Thank you very much for the help.

RE: Code inside vs. outside tasks

Posted by Richard Damon on November 4, 2011
My general rule is hardware initilzation (which tends to want to be done before interrupts are put "on the air") and the creating of communication resources (queue, semaphores, and mutes) generally want to be done before the scheduler starts. Sometimes a device needs a longer "configuration" protocol that might go into the beginning of a task, especially if it needs delays or interrupt responses.

[ 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