vTAL with small v aims to provide a standard interface for using multiple of virtual timers simultaneously while a one physical timer is presented on the target system.
vTAL represents standard APIs call for the application layer of a certain software while underneath providing low level APIs calls of the physical timer so it can be ported on any system and get the benefit of using so many virtual timers as you want while the system has only one hardware timer.
The project is mainly aimed to be used in an embedded software environment but also, it can be used with Linux/Windows OS environment.
The project consists of two main parts which are standarized as shown in the following figure:
- vTAL (Virtual Timer Abstraction Layer).
- HTAL (Hardware Timer Abstraction Layer).
This is the part which involves with the application developing. It is very abstracted so you don't feel the details of the hardware timer.
This layer contains standard APIs which each one expected to do a certain functionlity such that vTAL algorithm for handling too many virtual timers can work properly. It implies the details implementation of the working with the hardware timer.
- To use vTAL, you only need to write the implementation of HTAL APIs for the target system. And write it for a single shot timer case.
- The implementation of vTAL doesn't depend on memory allocation on heap. Only array in the stack and the size is configured from vTALConfig.h
- Nice interface of anything exist around.
- Written only in C and compliant to ISO 9899:1990 as possible.
- Any OS based on Linux Kernel(> v2.6)
- Stellaris LM4F120XL (ARM based) using one physical 32-bit timer. (WTIMER0A)
- AVR Atmega16/32 using 8-bit timer.(Timer0)
- Port & Test it on Windows.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent