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


xTimerStop does not always work first time

Posted by Bryn Smith on July 10, 2013
I am running a software timer with a 1 tick period which is started from an ISR (using xTimerStartFromISR) and then stops itself (using xTimerStop).

After the call to xTimerStop returns pdPASS the timer will sometimes continue running. This comes as a surprise to me as the timer.c code looks like it processes all the commands in the queue between invocations of the timer handler.

My current workaround is to use a local flag to indicate if the timer should be stopped and try calling xTimerStop again.

RE: xTimerStop does not always work first time

Posted by Bryn Smith on July 10, 2013
Forgot to mention this is FreeRTOS version 7.4.0

RE: xTimerStop does not always work first time

Posted by Dave on July 10, 2013
When you send the stop command the command is posted to a queue that is drained by the timer service task, so the return value indicates the command was sent to the queue not that the command has been processed. When the command is processed depends on the priority of the timer service task. If the timer service task has the highest priority of all your tasks then it will get processed right away.

I'm not sure it is viable to have a software timer that has the same frequency as the tick. The tick sets the time base, so if your software timer time period is exactly the system time base then it will need to run all the time. Maybe it is preventing the command being processed?

RE: xTimerStop does not always work first time

Posted by Bryn Smith on July 11, 2013
I use timers as Task alternatives for most modules in my system as they:
1) share a stack, saving a significant amount of RAM.
2) run cooperatively, simplifying shared data access

This particular 'timer' is effectively a block of code which runs on an event triggered by an ISR. I *could* have done it with a task, but it would be sitting there 99.99% of the time hogging stack space and doing nothing.

Certainly I am aware that this is not what timers were designed for, but I expected that the stop command (called from the timer handler) would be processed before the timer handler was invoked again.

[ 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