Misplaced Pages

Operating system abstraction layer

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Application programming interface
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Operating system abstraction layer" – news · newspapers · books · scholar · JSTOR (June 2024) (Learn how and when to remove this message)

An operating system abstraction layer (OSAL) provides an application programming interface (API) to an abstract operating system making it easier and quicker to develop code for multiple software or hardware platforms. It can make an application less dependent on any one specific operating system.

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-time operating systems (such as vxWorks, eCos, RTLinux, RTEMS). Implementations may also be provided for non real-time operating systems, 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 build automation (e.g., set of makefiles) to 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 real-time operating system. It also allows for embedded system software to be developed and tested on desktop workstations, providing a shorter development and debug time.

Implementations

  • TnFOX
  • MapuSoft Technologies - provides a commercial OS abstraction implementation allowing software to support multiple RTOS operating systems.
  • ClarinoxSoftFrame – middleware which provides OS abstraction targeting wireless embedded device and system development. It comprises wireless protocol stacks, development tools and memory management techniques in addition to the support of desktop and a range of real-time operating systems
  • IBM's Rhapsody
  • ACE

References

  1. Beningo, J. (2022). "Embeded Software Architecture Design". Embedded Software Design. Berkeley, California: Apress. pp. 29–52. doi:10.1007/978-1-4842-8279-3_2. ISBN 978-1-4842-8279-3.

External links

Category: