forked from RIOT-OS/RIOT
-
Notifications
You must be signed in to change notification settings - Fork 0
Timer Task Force
Kaspar Schleiser edited this page Jan 28, 2015
·
7 revisions
This page is used to collect requirements and suggestions concerning a hwtimer/vtimer/RTC redesign.
- very efficient timers for use in time-critical drivers
- easy-to-use interface
- Wait for a time period
- Await a point in time
- Wait for a (past) time + x
- (use RTC if available for super-long-time timers)
- what granularity to use? msec,usec,nsec, timer ticks, a combination?
-
timer.h: timer hardware abstraction, using ticks
-
hwtimer: low-level timer multiplexing, one timer.h timer using the same ticks
-
vtimer: higher-level timer multiplexing, using one hwtimer, usecs
-
first two look OK, are stable
-
vtimer sucks
RIOT - The friendly Operating System for the Internet of Things
Homepage | [GitHub] (https:/RIOT-OS/) | Developers Mailing List | Users Mailing List | Twitter @RIOT_OS
- Family: ARM
- Board: Airfy Beacon
- Board: Arduino Due
- Board: CC2538DK
- Board: HikoB Fox
- Board: IoT LAB M3
- Board: LimiFrog-v1
- Board: mbed_lpc1768
- Board: MSB-IoT
- Board: MSBA2
- Board: Nucleo-L1
- Board: Nucleo-F334
- Board: Nucleo-F303
- Board: Nucleo-F091
- Board: Mulle
- Board: OpenMote
- Board: PCA1000x (nRF51822 Development Kit)
- Board: Phytec phyWAVE-KW22
- Board: RFduino
- Board: Samr21 xpro
- Board: Spark Core
- Board: STM32F0discovery
- Board: STM32F3discovery
- Board: STM32F4discovery
- Board: UDOO
- Board: yunjia-nrf51822
- Family: ATmega
- Board: Arduino Mega2560
- Family: MSP430
- Board: MSB-430H
- Board: TelosB
- Board: WSN430
- Board: Zolertia Z1
- Board: eZ430-Chronos
- Family: native
- Board: native
- Family: x86
- Board: Intel Galileo