Operating system abstraction layer: Difference between revisions

Revision as of 14:47, 3 April 2012

Revision as of 15:02, 3 April 2012

Line 1:

An '''operating system abstraction layer''' ('''OSAL''') provides an [[application programming interface]] (API) to an [[Abstraction (computer science)|abstract]] [[operating system]] making it easier and quicker to develop code for multiple [[software]] or [[computer hardware|hardware]] platforms.

OS abstraction layers deal with presenting an abstraction of the common system functionality that is offered by any Operating system by the means of providing meaningful and easy to use Wrapper functions that in turn encapsulate the system functions offered by the OS to which the code needs porting. A well designed OSAL provides implementations of an API for several Real[[real-time Timeoperating Operating Systemssystem]]s (such as [[vxWorks]], [[eCos]], [[RTLinux]], [[RTEMS]]). Implementations may also be provided for non Real Timereal-time Operatingoperating Systemssystems, allowing the abstracted software to be developed and tested in a developer friendly desktop environment.

In addition to the OS APIs, the OS Abstraction Layer project may also provide a [[hardware abstraction layer]], designed to provide a portable interface to hardware devices such as memory, I/O ports, and [[non-volatile memory]]. To facilitate the use of these APIs, OSALs generally include a directory structure and set of [[makefiles]] that facilitate building a project for a particular OS and hardware platform.

Implementing projects using OSALs allows for development of portable embedded system software that is independent of a particular Realreal-time Timeoperating Operating Systemsystem. It also allows for embedded system software to be developed and tested on desktop workstations, providing a shorter development and debug time.

== Implementations ==